Skip to main content
Glama

record_finding

Record a conclusion about a service, repo, or customer so it appears on the entity's timeline and project Overview. Capture the finding, a one-word verdict, a short headline, and the next step a person should take.

Instructions

Record what you concluded about an entity (a service, a repo, a customer) in the project. It lands on the entity's timeline next to the Tares agents' findings and in the project's activity, under your key's name. finding is markdown; verdict one lowercase word (for example rca or resolved); label the label the entity is a value of when it is not the project's usual one (for example service). headline is one line (at most 100 characters) saying what you found, and next_step what a person should do (empty when nothing needs doing): both show on the project's Overview.

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": {
      "entity": "<entity>",
      "finding": "<finding>"
    },
    "name": "record_finding"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNo
entityYes
findingYes
projectNo
verdictNo
headlineNo
next_stepNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose meaningful effects: the finding appears on the entity's timeline alongside Tares agent findings, in project activity, and under the calling key's name — useful visibility and attribution context for a write. It does not say whether repeated calls overwrite, whether an unknown entity is created, or what permissions are needed, so key mutation semantics remain unclear.

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?

Front-loaded: purpose first, then downstream effect, then a compact backticked parameter key. Dense but no filler sentences; the parameter rundown is a single long sentence that stays readable, though it could be broken for scanability.

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

Completeness4/5

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

For a 7-parameter, unannotated write tool this is close to sufficient: purpose, effect, visibility, and most field semantics are covered, and an output schema exists so return values needn't be explained. The gaps are the undocumented 'project' parameter and the lack of guidance on entity resolution or repeat-call behavior.

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 coverage is 0%, so the description must compensate, and it does for most fields: 'finding' is markdown, 'verdict' a single lowercase word (with examples rca, resolved), 'label' the entity's label when it differs from the project default (example service), 'headline' one line capped at 100 characters, 'next_step' human action with empty meaning none. Only 'project' is left undefined, and 'entity' vs 'label' is described conceptually rather than as a lookup key.

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+resource: record a conclusion about a named entity (service, repo, customer) into a project, and names the destinations (entity timeline, project activity). An agent can distinguish it from record_review or record_milestone_check by the entity-scoped, free-form 'finding' framing, though no sibling is named explicitly.

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 by 'Record what you concluded' — appropriate after an investigation — but there is no explicit when-to-use/when-not, no prerequisites (does the entity need to exist?), and no comparison to the related record_* siblings. The agent must infer the trigger condition.

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