Skip to main content
Glama

NS Pros MCP Gateway

numverify__research_row

Claygent-style per-row research: answer ONE question about ONE company and return a JSON object matching your output_schema, with every field wrapped in its own evidence, {value, evidence_url, quote, status}. status is NEVER self-reported by the model: "found" means this code independently verified the model's quote is a VERBATIM substring of text actually fetched; "inferred" means a value was given but the quote could not be verified; "not_established" means no source answered the field, and it

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entity": {
        "name": "Stripe",
        "domain": "stripe.com"
      },
      "sources": "web",
      "max_cost": 0.02,
      "question": "Does this company sell to healthcare, and who is the head of sales?",
      "output_schema": {
        "properties": {
          "head_of_sales": {
            "type": "string"
          },
          "sells_to_healthcare": {
            "type": "boolean"
          }
        }
      }
    },
    "name": "numverify__research_row"
  }
}

Input Schema

NameRequiredDescriptionDefault
entityYesThe row/company to research. At least one of name/domain required.
sourcesNoWhere to look: "web" (company site only), "catalog" (entity_profile only), "both" (default).
max_costNoCost ceiling in US dollars for this one row. Default 0.02, max 0.50, minimum viable 0.002 (below that the call is refused rather than silently exceeding it).
questionYesThe question to answer about this company, in natural language, e.g. "Does this company sell to healthcare, and who is the head of sales?"
output_schemaYesJSON Schema object naming the fields to extract, e.g. {"properties":{"sells_to_healthcare":{"type":"boolean"},"head_of_sales":{"type":"string"}}}. Up to 20 fields.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: independent verbatim-quote verification, and the found/inferred/not_established status semantics. However the text is cut off mid-sentence ('...and it'), so the not_established explanation is truncated, and nothing is said about cost refusal behavior, failure modes, or what happens when web fetch fails.

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

Conciseness2/5

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

The surviving text is dense and front-loaded, but the description terminates mid-sentence at 'and it', leaving a dangling clause and an incomplete definition of the status enum. A truncated description is a structural defect, not conciseness.

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 five-parameter, nested-object research tool with no annotations and no output schema, the description does well to explain the {value, evidence_url, quote, status} return contract. But the truncated enum definition and the absence of any statement about cost enforcement or source-fetch fallback leave the agent without information it needs to interpret results 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 coverage is 100%, so all five parameters (entity, sources enum, max_cost, question, output_schema) are already documented with examples in the schema. The description adds the evidence-wrapping contract for output_schema fields, which is genuine value beyond the schema, but adds nothing for the other four parameters.

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?

States a concrete verb+resource: answer ONE question about ONE company and return an output_schema-shaped JSON object with per-field evidence. The single-question scope implicitly distinguishes it from a broader deep_research sibling, but no sibling is named and 'Claygent-style' is unexplained jargon an agent may not know.

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?

The 'ONE question about ONE company' framing implies this is the narrow, per-row extraction tool, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative. The agent must infer routing from scope wording alone.

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.