Skip to main content
Glama

Zoeb Nomi

Verify a claim about Zoeb Nomi

verify_claim
Read-onlyIdempotent

Check a claim or number about Zoeb Nomi against what zoebnomi.com states. Returns found, number_mismatch or not_found, with the site quote, source URL, evidence link, n and date where the site gives them. Use the returned quote, not your own paraphrase. A word lookup: it cannot see negation, so read the quote.

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": "verify_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
claimYesThe claim to check, e.g. "CrossSource lifted citation precision to 0.994".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the exact outcome vocabulary (found, number_mismatch, not_found) and the evidence payload (quote, source URL, evidence link, n, date where available). Most importantly it warns of a real behavioral limitation — a word lookup that cannot see negation — which the agent could not learn from annotations or schema.

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?

Three short sentences, front-loaded with what is checked and against what source, then the return states, then the operational caveat. Nothing is redundant and the negation warning is placed last for emphasis without burying the core definition.

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?

No output schema exists, so the description correctly compensates by enumerating return statuses and evidence fields, and it flags the negation blind spot. The remaining gap is minor: it does not say how to interpret or act on not_found versus number_mismatch, though the status names are largely self-explanatory.

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?

There is a single parameter with 100% schema description coverage, including a concrete worked example, so the schema already carries the semantics. The description adds no further constraints (length bounds, phrasing guidance) beyond what the schema states; baseline 3 applies.

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 gives a specific verb and resource ("Check a claim or number about Zoeb Nomi") and pins the source of truth (zoebnomi.com), plus it scopes the tool as a literal word lookup. It does not explicitly contrast itself with siblings like check_citations, so an agent must infer the boundary from the narrow subject matter.

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 context is implied by "a claim or number about Zoeb Nomi against what zoebnomi.com states," and there is a directive about how to consume output ("Use the returned quote, not your own paraphrase"). However, there is no explicit when-not guidance, no statement of prerequisites, and no named alternative for claims outside zoebnomi.com.

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.