Skip to main content
Glama

Classify Row

classify_row
Read-onlyIdempotent

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 to fetch the homepage once as a fallback. No text and no domain means every label is not_established with no model call made.

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": "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. Changed2 schema fields changed
    • changedInput schema / properties / entity / properties / domain / description
      Previous value: -"Company website domain — used to fetch the homepage ONLY when text is not provided."New value: +"Company website domain, used to fetch the homepage ONLY when text is not provided."
    • changedInput schema / properties / text / description
      Previous value: -"Text to classify directly (a description, a page you already fetched, etc.) — cheapest path, skips any fetch."New value: +"Text to classify directly (a description, a page you already fetched, etc.), cheapest path, skips any fetch."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, but the description adds substantial behaviour beyond them: cost profile of one small model call, that fetching is a single homepage request only as fallback, that 'found' requires the quote be independently verified as a verbatim substring, and that the no-input case short-circuits to not_established without spending a model call. Those are exactly the traits an agent needs to reason about cost and trust in the results.

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?

Dense but front-loaded: the identifier, usage shape and cost are in the first sentence, then the evidence contract, then the input routing. The inline return-shape listing is a little lengthy, but every clause carries operational information and none is filler.

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, yet the description spells out the returned per-label structure including the found|inferred|not_established status semantics and what verification means, plus the degenerate no-input behaviour. For a 3-parameter tool with nested entity, nothing an agent needs to invoke it correctly 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 still adds meaning beyond the schema by stating the precedence between text (cheapest, skips any fetch) and entity.domain (fetched only when text is absent) and by describing what each returned label object contains. This resolves the interaction between the two input paths rather than merely restating field docs.

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 (classify a row against candidate labels), gives the concrete usage shape (tagging a list by industry, ICP fit), and anchors itself against the sibling research_row by referencing its shared evidence contract, so an agent can tell what this does and how it differs from research-heavy 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 explicit operational routing: pass text directly as the cheapest path, use entity.domain to fetch the homepage once as a fallback, and notes that with neither input every label returns not_established with no model call. It covers the input-precedence case well but stops short of saying when to prefer this over siblings like research_row or deep_research for richer evidence.

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.