Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__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": "nsf-awards__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.5/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: it discloses cost/latency ("one small model call"), the fetch side effect (domain used to fetch the homepage only when text is absent), and the verification semantics ("found" only when the quote is an independently verified verbatim substring). It also describes the return shape per label since no output schema exists.

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?

Content is front-loaded with the core purpose and every clause carries information (cost, input choice, return contract, verification rule). Structure suffers from comma splices and a dangling appositive ("the most common GTM/AI usage shape..."), plus an unclosed quote around "found," but nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter tool with a nested entity object and no output schema, the description covers cost, input modes, fetch behavior, and the per-label return contract. Minor gaps remain: what happens when no domain resolves and whether classification can proceed from name alone are not addressed.

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 does add a genuine semantic distinction — text is the cheapest path that skips fetching, while entity.domain triggers a homepage fetch — which clarifies the tradeoff between the two mutually substitutable inputs. It adds only marginally beyond the schema text, which already states both points.

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?

"Cheap categorization: given a company and a list of candidate labels, decide which labels apply" states a specific verb (categorize/decide) and resource (labels for a company) with the key qualifier "cheap," and it explicitly anchors itself to the sibling research_row by sharing its evidence contract. An agent can distinguish this from deep_research or research_row without opening a schema.

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 routing between its two input modes: "Pass text directly (cheapest, no fetch) or entity.domain," and the "one small model call" phrasing signals when this is preferable to a heavier research tool. It stops short of an explicit "do not use this when you need X" exclusion or a direct comparison to research_row beyond the shared evidence contract.

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.