Skip to main content
Glama

NS Pros MCP Gateway

numverify__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": "numverify__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.0
Behavior4/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 well: it discloses cost ('cheap', 'one small model call'), the fetch behavior (homepage fetch only when text is not supplied), and the verification guarantee behind `status: found` (quote must be a verbatim substring of the source text). It omits auth requirements, rate limits, and how long text affects cost or truncation.

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 leading 'Cheap categorization' front-loads the key value, and every clause (cost, evidence contract, input mode) carries information. The final fragment 'or entity.domain' is a dangling construction and the middle sentence is run-on, which costs a point.

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?

There is no output schema, and the description compensates by spelling out the returned record shape and the meaning of each status (`found` vs `inferred` vs `not_established`) plus the verification rule. Combined with 100% schema coverage on all three parameters, the definition is nearly call-complete; only edge cases like oversized text or missing name/domain are unaddressed.

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 real meaning: `text` is the cheapest path that skips fetching, `entity.domain` is a fallback for homepage retrieval only, and `labels` are candidates to be tested rather than asserted. The 2–30 bound and nested entity fields are left to the schema.

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 concrete verb and resource: given an entity plus candidate labels, decide which labels apply, with an example use case (industry tagging, ICP fit). It is specific about the transformation performed. It does not differentiate itself from the many sibling `*__classify_row` tools from other providers, so it stops short of 5.

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 explicit routing advice for the two input modes: 'Pass text directly (cheapest, no fetch) or entity.domain', and the schema-side note that domain is used only when text is absent. It also frames the common usage pattern (tagging a list by industry/ICP). It doesn't say when to prefer a sibling tool or when this tool is a poor fit (e.g., very long text, ambiguous labels).

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.