Skip to main content
Glama

Check claims against the board

verify_claim
Read-onlyIdempotent

Use before you state a specific fact about a board the signed-in user can review, to check it against the design rather than your memory: give the component references, net names, pin-to-net connections, or finding ids your answer relies on, and this reports for each whether it actually exists in the board's current version and what is really there. Requires board review permission; unrelated public boards are excluded. It is not an opinion about your conclusion. It only tells you which of the things you are about to cite are real. Anything reported as refuted or unknown must not appear in your answer as fact. Checks up to 25 items in one call, so verifying is cheaper than not verifying.

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": {
      "board": "<board>"
    },
    "name": "verify_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
netsNoNet names you are about to cite, e.g. ["GND","+3V3"].
boardYesA personal board, or an organisation board with read:org consent and check permission: handle/slug or a boardrepo.com URL. Discover it with list_my_boards; do not guess one.
versionNoWhich saved version to read: a version number (3 or "v3"), a versionId from list_board_versions, "latest", or a release tag such as "rev-A". Omit for the latest version. Results echo the version they read; pass its id back to stay on it.
findingsNofinding_id values from review_board you are about to cite.
componentsNoReference designators you are about to cite, e.g. ["U1","C14"].
connectionsNoPin-to-net connections you are about to assert, e.g. [{"ref":"U1","pin":"12","net":"GND"}]. Omit pin to assert only that the part touches the net.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds substantial context they cannot carry: board review permission is required, unrelated public boards are excluded, a 25-item per-call cap exists, and results echo the version read so the caller can pin to it. It also defines the outcome vocabulary ("refuted or unknown must not appear in your answer as fact"), which is exactly the behavioral contract an agent needs.

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?

It is front-loaded with the trigger, then eligibility, then the interpretation rule, and every clause carries information. The pair of sentences "It is not an opinion about your conclusion. It only tells you which of the things you are about to cite are real" restates the same boundary twice and could be tightened.

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?

For a six-parameter verification tool with an output schema, the description covers everything the schema cannot: when to call it, permission prerequisites, board exclusions, batching limits, version pinning, and how to treat refuted or unknown results. Nothing an agent needs in order to call it correctly or interpret the response is missing.

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 100%, so the baseline is 3; the description still adds value by explaining that the four array parameters are the items "your answer relies on" and that one call checks up to 25 items, clarifying the batching model behind maxItems. The version echo-and-pass-back hint also gives semantics the schema only partly conveys.

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?

"Check a specific fact about a board against the design rather than your memory" names a concrete verb and resource, and the enumerated claim types (component references, net names, pin-to-net connections, finding ids) make the scope unambiguous. It is clearly distinguishable from siblings like query_design or read_schematic, which fetch design data rather than adjudicate claims the agent is about to make.

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?

"Use before you state a specific fact about a board the signed-in user can review" gives an explicit trigger and eligibility condition, and "verifying is cheaper than not verifying" supplies the cost argument for preferring it. It also bounds scope ("not an opinion about your conclusion"). It does not name a sibling tool as an alternative, which keeps it short of a 5.

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