Finbolt

verify_evidence

Full evidence for the claims of one verify call on your account: each claim's span, parsed figure, verdict, reason, tolerance and the filings read, with tag, accession, link, period and source credit.

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": {
      "record_id": "<record_id>"
    },
    "name": "verify_evidence"
  }
}

Input Schema

Name	Required	Description	Default
`claim_ids`	No	Optional: only these claims (default: all)
`record_id`	Yes	The record_id a verify call returned

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 29, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral burden. It usefully discloses the returned evidence contents, including spans, verdicts, reasons, tolerances, and filing metadata, but it does not explicitly state read-only behavior, side effects, authentication needs, or rate limits.

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 a single front-loaded sentence that immediately states the resource and then enumerates the evidence returned. It is dense but every listed field is relevant to understanding the payload.

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?

Given a complete input schema and an existing output schema, the description provides enough context to identify the tool and its evidence payload. A stronger definition would explicitly connect record_id to a prior verify call and state that this is a read-only retrieval operation.

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 description coverage is 100%, so record_id and claim_ids are already documented. The description refers to 'one verify call' and 'claims,' which lightly maps to the parameters, but it adds no syntax or filtering semantics beyond the schema.

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 clearly identifies the resource: full evidence for the claims of one verify call, including the specific evidence fields returned. It references the related verify call and record context, so an agent can distinguish it from sibling tools like verify, though it lacks an explicit retrieval verb.

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 only implied by the phrase 'of one verify call on your account,' which suggests this should be called after verify returns a record. It does not explicitly state when to use this tool versus verify or other siblings, nor does it give exclusions.

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

All Finbolt tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?