Skip to main content
Glama

NS Pros MCP Gateway

ntsb-investigations__classify_row

Cheap categorization: given a company and a list of candidate labels, decide which labels apply, the most common GTM/AI usage shape (tagging a list by industry, ICP fit, etc.), one small model call. Same evidence contract as research_row: each label comes back {label, applies, evidence_url, quote, status: found|inferred|not_established}, "found" only when the model's quote is independently verified as a verbatim substring of the text used. Pass text directly (cheapest, no fetch) or entity.domain

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"
      },
      "labels": [
        "healthcare",
        "fintech",
        "logistics"
      ]
    },
    "name": "ntsb-investigations__classify_row"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoText to classify directly (a description, a page you already fetched, etc.), cheapest path, skips any fetch.
entityYesThe row/company to classify. At least one of name/domain required.
labelsYesCandidate labels to test, 2-30 strings, e.g. ["healthcare","fintech","logistics"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses cost profile ('one small model call'), the conditional fetch behavior (domain used to fetch the homepage ONLY when text is not provided), and the full evidence contract including the critical verification rule that 'found' requires the quote to be a verbatim substring of the source text. That verification semantics is exactly the kind of behavioral trait an agent could not infer from structured fields.

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?

Purpose and cost lead, then the evidence contract, then the input-path guidance — a sensible front-loaded order. It is a dense run-on sentence with an embedded brace-delimited return shape that reads awkwardly, but nearly every clause carries information.

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?

There is no output schema, and the description fully compensates by enumerating the per-label return fields (label, applies, evidence_url, quote, status) and the three status values. Combined with the cost and fetch notes, an agent has everything needed to invoke this correctly and interpret the result.

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; the description still adds value by stating the precedence between `text` and `entity.domain` (direct text skips the fetch) and by explaining what a label result contains. It does not restate the 2-30 label bound, which is left to the schema, so it is slightly above baseline rather than fully additive.

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?

States a specific verb and resource: 'given a company and a list of candidate labels, decide which labels apply'. It also names the sibling it relates to (research_row) and its own distinguishing trait ('Cheap categorization', 'one small model call'), so an agent can tell it apart from the heavier research tools.

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

Usage Guidelines4/5

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

Gives concrete routing guidance for the two input paths: 'Pass text directly (cheapest, no fetch) or entity.domain', and frames the common scenario ('tagging a list by industry, ICP fit'). It stops short of an explicit when-not-to-use rule (e.g., when to prefer research_row or entity_profile instead), which keeps it below a 5.

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.