Skip to main content
Glama

Control: record that it was done

control_evidence

Record that a control was performed, with the fingerprint of the evidence (screenshot, export, report). Hash-chained, so evidence cannot be back-dated after the fact without it showing. Requires the organization API key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "control_id": "<control_id>",
      "performed_by": "<performed_by>",
      "document_sha256": "<document_sha256>"
    },
    "name": "control_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
control_idYes
performed_atNoWhen it was done (ISO 8601). Default: now
performed_byYes
document_sha256YesSHA-256 fingerprint of the document (64 hex characters); the file stays with you

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the hash-chaining guarantee and its consequence — evidence 'cannot be back-dated after the fact without it showing' — which is exactly the kind of integrity/immutability context annotations cannot convey. It also names the auth requirement (org API key). It stops short of saying what happens on a duplicate submission, notably relevant given idempotentHint=false.

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

Conciseness5/5

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

Three short sentences, front-loaded with the action, then the integrity guarantee, then the auth requirement. No filler or repetition of the title.

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

Completeness3/5

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

For a mutation tool with no output schema and 40% parameter coverage, the description covers the conceptual core and the trust property well, but omits the return shape, duplicate-handling behavior, and whether control_id must reference an existing control. These gaps matter for correct first-call invocation.

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

Parameters3/5

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

Schema coverage is only 40%, so the description has to compensate. It defines what document_sha256 conceptually represents (the fingerprint of a screenshot/export/report), but control_id, performed_by, and note are left without meaning in the description, and the hash-chaining framing is not tied to any specific argument.

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

Purpose4/5

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

States a specific verb and resource: 'Record that a control was performed, with the fingerprint of the evidence.' The parenthetical examples (screenshot, export, report) make it concrete. It does not, however, differentiate itself from the sibling control_save, so an agent cannot be certain which of the two is the recording path.

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

Usage Guidelines3/5

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

Usage is implied (call this after a control is performed and you have a document hash) and one prerequisite is stated outright: 'Requires the organization API key.' But there is no explicit when-to-use versus control_save or ledger_evidence_bundle, and no guidance on whether the control must already exist before recording.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources