Skip to main content
Glama
Sign In
tech-recall

tech-recall

by WItaZhang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

record_verification

Caches source verification results for a specific task and revision without overwriting the card, recording status, maintenance, and evidence; use unknown when checks fail.

Instructions

Cache actual source checks for this task/revision only. No card overwrite. Use unknown on failure.

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": {
      "task_id": "<task_id>",
      "card_id": "<card_id>",
      "revision": "<revision>",
      "verification": "<verification>"
    },
    "name": "record_verification"
  }
}

Input Schema

NameRequiredDescriptionDefault
card_idYes
task_idYes
revisionYes
verificationYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

Beyond the annotations, the description discloses important behavior: the write is scoped to the task/revision, it does not overwrite the card, and unknown should be used on failure. This is meaningful context for a non-read-only but non-destructive operation, though it omits persistence or idempotency details.

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 short and front-loaded, with each fragment adding some constraint or failure guidance. The phrasing 'actual source checks' is somewhat cryptic, but there is little wasted text.

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

Completeness2/5

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

This is a relatively complex tool with four required parameters, a nested verification object, an evidence array, and no schema parameter descriptions. The description gives useful scope and failure guidance but leaves most input semantics unexplained, so it is incomplete for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the burden of explaining the four required parameters. It references task/revision, card, and the unknown status value, but it does not explain card_id, revision, or the nested verification fields such as evidence, maintenance, and summary.

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?

The description states a specific action and scope: caching actual source checks for this task/revision only. It also clarifies that no card overwrite occurs, which helps distinguish it from card mutation tools, though it does not name a sibling alternative 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?

It implies when to use the tool by saying to cache checks for this task/revision only and to use unknown on failure. However, it does not explicitly compare this tool with alternatives such as confirm_card or manage_card, so the agent must infer when this is the right choice.

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

Deploy Server

Other Tools