Skip to main content
Glama

Geoa — Get found in ChatGPT

Verify Claim Against Source

geoa_verify_claim
Read-onlyIdempotent

Verify a numeric claim against its cited source (geoa's Gate). Fetches the source page and checks mechanically whether the number appears there and whether the source is circular; with a geoa account it also checks SEMANTICALLY whether the source actually supports the claim. Returns a verdict: supported | unsupported | self_referential | unverifiable, plus the matched evidence.

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": "<claim>"
    },
    "name": "geoa_verify_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
claimYesThe claim containing the number, e.g. '68% of searches end without a click'
source_urlNoURL of the source the claim cites

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds substantial operational detail beyond that: fetching the source page, mechanical presence and circularity checks, account-gated semantic checking, and the exact verdict categories returned.

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 front-loaded and compact: purpose, method, account-dependent behavior, and return verdicts are all covered without repetition or filler.

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?

Even without an output schema, the description explains the possible verdict values and evidence returned. Together with the annotations and fully documented input schema, an agent has enough information to invoke and interpret the tool correctly.

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 both parameters are already well documented. The description reinforces that the claim is numeric and the URL is the cited source, but it adds little parameter-level syntax or format detail beyond the schema.

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?

States a specific verb and resource: verify a numeric claim against its cited source. It names the mechanical checks, optional semantic check, and concrete verdicts, making it clearly distinguishable from the account, article, and radar sibling tools.

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?

The intended use case is clear from the first sentence and the account-dependent semantic check gives useful context. It does not explicitly name when not to use it or compare against alternatives, but no sibling tool is a close substitute.

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