Skip to main content
Glama

SendGrid (Unofficial)

Research Row

research_row
Read-onlyIdempotent

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 its value is always null, never guessed, never a blended score. Sources: "web" fetches the company's own site (entity.domain required, homepage, /about, /leadership) via fetch_url; "catalog" checks entity_profile (SEC EDGAR; resolved:false for a private company is expected, not a failure); "both" (default) tries both. max_cost (USD, default 0.02, max 0.50) scales how many pages are fetched and refuses up front if it is too small to pay for even one extraction call (floor $0.002), never silently overspends. A row where every source comes back empty costs nothing: every field is mechanically not_established with NO model call made. For a boolean/derived field (e.g. "does this company sell to healthcare"), the quote only has to SUPPORT the value, a descriptive sentence about customers/products counts, the source need not state the answer verbatim. leadership_page_status ("fetched"|"not_found"|"not_attempted", plus leadership_note) says plainly whether a leadership/team page was actually read, so a named-person field (head_of_sales) coming back not_established is distinguishable from "this company just doesn't publish one" vs. "we never checked". model_output_empty:true means the model returned nothing usable (a transport/budget problem), every field is not_established for THAT reason, never read as 20 individual "no" judgments. Use with a fixed question + schema across many rows for "Claygent over N companies with a hard cost cap" (composes with batch callers). For picking from a fixed label list instead of extracting open fields, use classify_row (cheaper, one model call).

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": "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. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well past the annotations: status is code-verified against verbatim quotes rather than self-reported, empty-source rows cost nothing and make no model call, max_cost has a floor of $0.002 below which the call is refused, and model_output_empty is flagged to prevent misreading as 20 'no' judgments. leadership_page_status distinguishes 'company doesn't publish one' from 'never checked'.

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

Conciseness4/5

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

Front-loaded with the core contract (one question, one company, evidence-wrapped JSON) and organized by concern: status semantics, sources, cost, edge cases, sibling routing. It is dense and some sentences pack multiple facts (e.g. the leadership/not_established clause), but essentially every clause earns its place.

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?

No output schema exists, yet the description fully specifies the return contract (value/evidence_url/quote/status wrapper, status enum meaning, leadership_page_status, model_output_empty). For a tool with 5 params, nested entity object and cost/verification complexity, nothing an agent needs to invoke or interpret it is missing.

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 meaning the schema lacks: entity.domain is a hard prerequisite for sources='web', max_cost scales page fetches and is enforced before spend, and output_schema fields get wrapped in {value, evidence_url, quote, status}. The cost floor and refusal behavior are not in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource+scope: 'Claygent-style per-row research: answer ONE question about ONE company and return a JSON object matching your output_schema'. It also explicitly contrasts itself with the closest sibling (classify_row for fixed label lists), so an agent can route without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the intended pattern (fixed question + schema across many rows, 'Claygent over N companies with a hard cost cap'), the alternative (classify_row, cheaper, one model call) and the selection condition. It also explains when each sources value applies ('web' requires entity.domain; 'catalog' SEC EDGAR; 'both' default).

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.