Skip to main content
Glama

NS Pros MCP Gateway

nobel__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": "nobel__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.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden, and it does valuable work by disclosing that return fields are wrapped in {value, evidence_url, quote, status} and that status is code-verified rather than self-reported. That verification model ('found' = verbatim substring of fetched text, 'inferred' = unverifiable quote) is exactly the kind of context annotations could not supply. The disclosure is weakened because the text is cut off mid-sentence at 'not_established ... and it', leaving the third status and any downstream consequences unexplained.

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 content is dense and front-loaded — purpose first, return contract second — with no filler sentences. But the definition is physically truncated mid-word ('and it'), which is a real structural defect an agent must work around when reasoning about the not_established case.

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?

There is no structured output schema, so the description is right to explain the evidence-wrapper return shape, and it does. For a tool with 5 parameters, nested entity objects, a cost ceiling, and a verification pipeline, though, the description omits failure behavior (what happens on refusal or when max_cost is below minimum), guidance on field limits beyond the schema, and a complete explanation of the not_established status.

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 the baseline of 3 applies; the schema already explains entity, sources enum, max_cost ceiling, and output_schema limits. The description adds only the 'ONE question about ONE company' framing, which is meaningfully narrower than the schema's natural-language question field suggests but is not parameter-specific detail.

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 states a specific verb and scope: 'per-row research: answer ONE question about ONE company and return a JSON object matching your output_schema.' That is far more than a restatement of the name and tells an agent exactly what a call produces. It stops short of naming which sibling to prefer (e.g. nobel__deep_research or nobel__classify_row), so the differentiation is implicit rather than explicit.

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 by the scoping language: one question, one company, per row — which signals batch/enrichment workloads rather than broad open-ended research. However, the description never names an alternative tool or states an exclusion ('do not use for multi-question deep dives; use deep_research'), and it offers no prerequisites beyond what the schema already declares for the domain field.

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.