Skip to main content
Glama

ck_finding

Record findings with governance decisions or disposition existing findings to clear audit trails and enforce policies.

Instructions

Record or disposition a governed finding. mode=create (default) persists a finding with a ruling decision (allow, warn, block, escalate_to_human); findings are the durable audit trail in ControlKeel. mode=resolve|dismiss|escalate disposition EXISTING findings so the agent that created them can also clear them: pass finding_id for a single finding, or rule_id/category/status to bulk-disposition all matching active findings in the session (resolve->approved, dismiss->rejected, escalate->escalated). Write operation. For create, required fields are session_id, category, severity, rule_id, plain_message; decision defaults to warn, use allow for an approved exception (which also auto-resolves matching open/blocked findings). Returns finding_id + status for create, or disposed_count + disposed_finding_ids for disposition. Use ck_finding to record and clear policy findings; use ck_memory_record for general knowledge not tied to a policy rule.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoFinding category (e.g., security, compliance, performance).
decisionNoGovernance decision: allow, warn, block, or escalate to human.
finding_idNoTarget finding id for single disposition (resolve/dismiss/escalate modes).
metadataNo
modeNocreate (default) records a finding. resolve/dismiss/escalate disposition existing findings, by `finding_id` (single) or `rule_id`/`category`/`status` (bulk).
plain_messageNoHuman-readable finding description.
reasonNoReason recorded on the finding(s) when dismissing.
rule_idNoPolicy rule identifier that triggered this finding.
session_idYesUnique session identifier for correlating findings, proofs, budget, and audit trail.
severityNoSeverity level (e.g., critical, high, medium, low).
statusNoBulk disposition filter: only findings currently in this status are dispositioned (e.g. blocked, open, escalated).
task_idNoTask identifier within the session for scoped operations.
titleNoHuman-readable title for display and search.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
contradicts_finding_idNo
disposed_countNo
disposed_finding_idsNo
extends_finding_idNo
finding_idNo
modeNo
precedentNo
requires_humanNo
resolved_finding_idsNo
resolved_findings_countNo
statusNo
summaryNo
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate readOnlyHint=false (write operation), and the description confirms 'Write operation' and details behavioral traits: create persists a finding with decision, disposition clears findings, allow auto-resolves matching open/blocked findings. No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a front-loaded summary and clear separation of create and disposition behaviors. However, it is somewhat verbose, repeating some schema descriptions. Could be trimmed without losing clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 13 parameters and the presence of an output schema, the description covers both create and disposition flows comprehensively, explains return values, and provides contextual examples. No major gaps identified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 92% (high), baseline is 3. The description adds meaning beyond the schema: explains mode behavior (create vs. disposition), notes default decision (warn), and clarifies allow's auto-resolution effect. This adds value, justifying a score above baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Record or disposition a governed finding' and defines two main modes (create vs. disposition). It explicitly distinguishes from the sibling tool ck_memory_record, which is for general knowledge not tied to a policy rule.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance: when to use create vs. disposition, how to target single or bulk findings, and when to use allow to auto-resolve. It also contrasts with ck_memory_record, giving clear when-not-to-use advice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aryaminus/controlkeel'

If you have feedback or need assistance with the MCP directory API, please join our Discord server