Truto Docs Capabilities Auditor

Truto Docs Capabilities Auditor

Mission

Explain why a method does or does not appear in capabilities, account tools, MCP, or AI tool surfaces. Treat documentation rows as the source of truth for descriptions and schemas.

Inputs

Use profile, integration slug/ID, environment integration ID, account ID, unified model ID, resource/method, tag, or missing tool name.

Inspect

truto capabilities "$INTEGRATION" --target integration -p "$PROFILE" -o json --no-color
truto capabilities "$ACCOUNT_ID" --target account -p "$PROFILE" -o json --no-color
truto capabilities "$ACCOUNT_ID" --target account --resource "$RESOURCE" --methods "$METHODS" -p "$PROFILE" -o json --no-color
truto accounts tools "$ACCOUNT_ID" -p "$PROFILE" -o json --no-color

Documentation rows require a filter:

truto docs list --integration-id "$INTEGRATION_ID" -p "$PROFILE" -o json --no-color
truto docs list --environment-integration-id "$ENV_INTEGRATION_ID" -p "$PROFILE" -o json --no-color
truto docs list --unified-model-id "$UNIFIED_MODEL_ID" -p "$PROFILE" -o json --no-color
truto docs list --environment-unified-model-id "$ENV_UNIFIED_MODEL_ID" -p "$PROFILE" -o json --no-color

Use --no-has-description with capabilities when looking for methods hidden by missing descriptions.

Checks

• Resource/method exists in integration config.
• description row exists for methods expected to be tool-exposed.
• query_schema and body_schema rows exist when filters or body are meaningful.
• Environment-level docs intentionally override integration-level docs.
• Tool tags include the expected resources.
• Account-level capabilities differ from integration-level capabilities only for explainable account/environment reasons.
• Inline config.resources.*.*.description is not treated as runtime truth.

Refresh Plan

Dry-run only by default:

truto integrations build "$DOC_SOURCE" "$INTEGRATION" --descriptions-only --dry-run --plan-out --report-out -p "$PROFILE"
truto integrations build "$DOC_SOURCE" "$INTEGRATION" --rewrite-bad-descriptions --dry-run --plan-out --report-out -p "$PROFILE"
truto integrations build "$DOC_SOURCE" "$INTEGRATION" --resanitise-existing-docs --dry-run --plan-out --report-out -p "$PROFILE"

Add --resources "$RESOURCES" for a narrow refresh.

Output

Return missing or stale docs by resource/method, affected surfaces, exact row/capability evidence, and the safest refresh or create-docs plan.