Skip to main content
Glama

NS Pros MCP Gateway

nvd__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": "nvd__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

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does disclose the key contract: each field is wrapped as {value, evidence_url, quote, status}, and status semantics (found = verbatim substring verified against fetched text, inferred = unverified, not_established = no source answered) are spelled out. That is exactly the kind of non-obvious behavior an agent needs; it loses a point only because the final sentence is truncated mid-thought ('and it'), leaving the not_established rule incomplete.

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

Conciseness3/5

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

It is front-loaded and dense with useful contract details, but the text is visibly truncated ('and it') and the single long sentence packs evidence semantics, status definitions, and return format together without structure, making it harder to parse than it needs to be.

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?

For a moderately complex nested-parameter tool with no output schema and no annotations, the description covers the essential extraction/evidence contract and the verification model. It is short of complete because the status definition is cut off and nothing is said about source selection or cost-ceiling behavior, though those live in the schema.

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 entity/domain, sources, max_cost, question, and output_schema are already fully documented in the schema. The description adds meaning about the return shape rather than about parameters, so the 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: 'answer ONE question about ONE company' returning a JSON object matching output_schema, wrapped in per-field evidence. That is far more precise than the many sibling '*__research_row' names, though it does not explicitly distinguish itself from alternatives like deep_research or bet_research.

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' scoping implies this is the per-row/single-entity path rather than a batch or deep-dive tool. However, there is no explicit when-to-use/when-not-to-use guidance and no mention of when to prefer a sibling such as deep_research or classify_row.

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.