Tool reference | Docs

Your coding agent calls these tools through the MCP connection. All tools operate on the connected project. list_issues, get_issue, and get_setup_status read data; report_fix records a deployed fix.

list_issues

Lists issues with their expected behavior, occurrence counts, and first and last observation times.

Input	Description
`status`	Optional filter: `expected`, `unexpected`, or `dismissed`. Omit to list all statuses.

Example input:

{ "status": "unexpected" }

Returns an issues array.

get_issue

Reads one issue's evidence, suggested checks, occurrences, and current fix with monitoring results.

Input	Description
`issueId`	Required issue UUID.

Example input:

{ "issueId": "7cde2790-b9c2-49e8-90bd-ef4352f953bb" }

Returns an issue object. When a fix has been reported, activeFix.evidence includes its monitoring status, the number of eligible traces evaluated, and recurrence and non-recurrence counts. Use these results to check how the deployed fix is performing.

get_setup_status

Reads connection details and checks whether a specific request reached Kensa.

Input	Description
`traceId`	Optional original application or Langfuse trace ID. Include it to verify a specific request; omit to inspect connection details.

Example input:

{ "traceId": "0123456789abcdef0123456789abcdef" }

Returns the project, connection URL, OTLP endpoint, and trace status:

traceReceived confirms receipt of the supplied trace ID.
lastTraceAt shows the latest trace update time.
productionMonitoringReady means Kensa received a production trace with a version in the last 24 hours. Monitoring a particular fix starts when that deployed fix is reported.

report_fix

Records a production deployment and starts monitoring for recurrence. Your coding agent assembles these inputs from the issue and verified deployment details. See Report a fix for the everyday workflow.

Input	Description
`issueId`	Required issue UUID.
`deployedVersion`	Required deployed version, matching `service.version` on the traces. The Kensa SDK's automatic detection uses the commit SHA.
`deploymentEnvironment`	Required: `"production"`.
`deployedAt`	Required deployment time as an ISO timestamp.
`commitSha`	Required: the 40-character lowercase commit SHA, or `null` when unavailable.
`idempotencyKey`	Required unique string generated for this report. Reuse it when retrying the same report.

Example input:

{
  "issueId": "7cde2790-b9c2-49e8-90bd-ef4352f953bb",
  "deployedVersion": "0123456789abcdef0123456789abcdef01234567",
  "deploymentEnvironment": "production",
  "deployedAt": "2026-09-22T04:00:00Z",
  "idempotencyKey": "refund-window-fix-2026-09-22",
  "commitSha": "0123456789abcdef0123456789abcdef01234567"
}

Returns a fix object with its deployment details and monitoring evidence.

Retries and subsequent fixes

Retry the same report with the same inputs and idempotencyKey. Reusing that key with different details returns idempotency_key_reused. Use a new key for a new report, which supersedes the previous fix for that issue. Reopen a dismissed issue before reporting a fix.

Kensa evaluates traces from the reported version and production environment that start after the report. See issue states for the monitoring results.