Skip to main content
Glama

SOQVER business facts (SO4AG)

Check a claim

check_claim
Read-only

Check one claim by its id: validity now, digest, dispute and attestations.

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": {
      "claim_id": "<claim_id>"
    },
    "name": "check_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
claim_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral signal, 'validity now', implying a point-in-time evaluation whose result may change, and it enumerates the response facets. It does not mention permissions, rate limits, or whether historical validity is available.

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?

A single front-loaded sentence with no filler; the resource and its id come first and the output facets follow. The comma-separated facet list is terse enough that 'digest' and 'attestations' read as bare labels rather than explained terms.

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 read-only, single-parameter tool with no output schema, the description should explain what the returned facets mean and what id form is accepted. It names the facets but leaves 'digest', 'dispute', and 'attestations' undefined, so an agent knows the shape of the answer but not how to read it.

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?

With one parameter at 0% schema description coverage, the description carries the burden and only partly discharges it: 'by its id' confirms claim_id identifies the claim, but nothing explains the URI format or 500-character limit the schema declares, nor where such an id comes from.

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?

"Check one claim by its id" gives a specific verb and a scoped resource (a single claim, keyed by id), and the trailing list names what the check yields: validity, digest, dispute, attestations. The singular framing implicitly contrasts with the plural sibling get_claims, 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 rather than stated: 'by its id' signals the tool is for looking up a single already-known claim, as opposed to listing claims. There is no explicit when-not-to-use, no mention of what to do without an id, and no named alternative.

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