Skip to main content
Glama
Sign In
Groundcheck

Groundcheck

by beepboop2025
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

check_citations

Fact-check all claims in a text block automatically, returning a per-claim report with verdict, sufficiency rating, and a signed receipt for verification.

Instructions

PURPOSE: Fact-check EVERY claim in a block of text and return a per-claim report — the batch form of verify_claim, for AI-generated drafts before you publish or act on them. GUIDELINES: each reported claim carries verdict, sufficiency (abstain/escalate on anything but 'sufficient'), and a conformal guarantee when certified; the response is covered by a signed receipt bound to a hash of your text, so you can prove which document was checked. Use verify_claim for a single claim. PARAMETERS: text = the prose (claims extracted automatically); maxClaims 1-20 (default 8). LIMITATIONS: skips questions/opinions, bounded by maxClaims, same source limits as verify_claim.

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": {
      "text": "<text>"
    },
    "name": "check_citations"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText whose factual claims should be checked.
maxClaimsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

No annotations were provided, so the description carries full burden. It discloses that the tool returns a per-claim report with verdict, sufficiency, and a conformal guarantee, plus a signed receipt. It also mentions limitations. However, it does not explicitly state if the tool is read-only or destructive, though the nature of fact-checking implies read-only.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with labeled sections (PURPOSE, GUIDELINES, PARAMETERS, LIMITATIONS) and is concise, packing essential information into a short paragraph without redundancy.

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 no output schema and no annotations, the description covers purpose, usage, parameters, limitations, and distinguishes from siblings. It includes details about the return format and receipt, which is sufficient for most use cases. The only minor gap is not specifying the exact structure of the claim report beyond verdict and sufficiency.

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?

The description adds context to the schema: 'text = the prose (claims extracted automatically)' and reiterates the range for maxClaims. Since schema coverage is 50%, the description compensates by clarifying the meaning of 'text' and that claims are extracted automatically.

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?

The description clearly states the verb (fact-check), resource (claims in a block of text), and explicitly distinguishes from the sibling verify_claim by noting it is the batch form. It also specifies the use case: AI-generated drafts before publishing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use the tool ('before you publish or act'), when not to ('Use verify_claim for a single claim'), and details limitations such as skipping questions/opinions and maxClaims bounds.

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