Skip to main content
Glama

NS Pros MCP Gateway

nplg-catalog__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": "nplg-catalog__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.8/5.0
Behavior4/5

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

With zero annotations the description carries the full burden and does unusually well: it defines the three status values and, critically, states that status is never model-self-reported and that "found" requires a verbatim substring match against fetched text. That is exactly the trust/verification behavior an agent needs. It loses a point because the final clause is cut off mid-sentence and nothing is said about failure modes or what happens when sources cannot be fetched.

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?

The purpose is front-loaded in the first clause, which is good, and the sentences are information-dense rather than padded. However the text terminates mid-sentence at "and it", leaving an incomplete thought, and the second half is a single sprawling clause that is hard to parse.

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?

For a 5-parameter tool with nested objects and a user-supplied output schema, the description supplies the one thing the schema cannot: how results come back and how evidence is verified. Given the truncation is minor and the schema documents every parameter, an agent has enough to call this correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema by explaining that every output_schema field is returned wrapped as {value, evidence_url, quote, status} and by defining the status enum semantics. It does not add anything about sources or max_cost beyond what the schema already documents.

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 names a concrete verb and resource — "answer ONE question about ONE company and return a JSON object matching your output_schema" — and the repeated "ONE" pins the scope to a single-entity, single-question lookup, which implicitly separates it from broader research siblings. It never names an alternative tool by name, so the differentiation is inferred from scope rather than stated.

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 is implied: call this when you have one question about one row and need evidence-backed fields. There is no explicit when-not guidance, no mention of when to prefer deep_research or entity_profile instead, and no note on batch invocation despite the "per-row" framing.

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.