Skip to main content
Glama

ck_finding

Create policy findings with governance decisions (allow, warn, block, escalate), and resolve, dismiss, or escalate existing ones to keep a durable audit trail.

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

Output Schema

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

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

The description discloses that 'mode=create' persists a finding and 'mode=resolve|dismiss|escalate' dispositions existing findings. It mentions that using 'allow' auto-resolves matching open/blocked findings, which provides behavioral insight beyond annotations. Annotations indicate a write operation (readOnlyHint=false), and the description confirms it without contradiction.

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 moderately long but each sentence adds necessary information. It front-loads the main action and mode distinction, then details parameters and returns. Minor redundancy could be trimmed, but overall it is efficient.

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?

The description covers all relevant aspects: modes, required fields, default behaviors, return values, and sibling differentiation. With output schema present, the return structure is clarified. For a tool with 13 parameters and multiple modes, the description is thorough and leaves no critical ambiguity.

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), so baseline is 3. The description adds value by explaining defaults (decision defaults to warn), special behavior (allow auto-resolves), and how bulk disposition works via rule_id/category/status, which is not fully detailed in the schema descriptions.

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 the tool's purpose: 'Record or disposition a governed finding.' It explains both create and disposition modes, and distinguishes from sibling 'ck_memory_record' by specifying that ck_finding is for policy findings while the sibling is for general knowledge.

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

Usage Guidelines4/5

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

The description provides explicit guidance on when to use each mode (create vs. disposition) and lists required fields for create. It directly recommends using ck_finding for policy findings and ck_memory_record for general knowledge, offering an alternative. It does not explicitly state when not to use the tool, but the context is clear.

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