Skip to main content
Glama

NS Pros MCP Gateway

nvd__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": "nvd__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.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses that this is a single small model call, describes the exact per-label output contract, explains that 'found' requires independent verbatim verification, and clarifies the status semantics (found|inferred|not_established). It also flags the cheapest execution path (no fetch when text supplied), which is critical behavioral context for an agent.

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?

The description is front-loaded with the core purpose and uses compact, information-dense phrasing. It is a bit run-on with comma-separated clauses, but nearly every sentence earns its place by adding execution or output-contract detail.

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 tool with a nested entity object, multiple input modes, and no output schema, the description supplies the missing return-value contract (per-label structure, status enum) and verification semantics. An agent has enough information to choose the input path and interpret results correctly.

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 is 3. The description largely restates what the schema already documents—that text is the cheapest no-fetch path and that domain is used to fetch the homepage only when text is absent—without adding new syntax, constraints, or label-selection semantics beyond 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?

The description opens with a specific verb and resource ('Cheap categorization: given a company and a list of candidate labels, decide which labels apply') and explicitly names the typical usage shape (tagging by industry, ICP fit). An agent can tell immediately what the tool returns ('which labels apply') and how it differs from a generic research or fetch tool.

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?

It gives concrete input-path guidance: 'Pass text directly (cheapest, no fetch) or entity.domain', making the cost trade-off explicit. It references 'same evidence contract as research_row' but does not explicitly say when to choose this over research_row or another classification route, leaving a minor gap in alternative-selection guidance.

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.