Skip to main content
Glama

NS Pros MCP Gateway

nobel__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": "nobel__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.3/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does substantial work: cost profile ("one small model call", "cheap"), the return shape per label, and the verification rule that "found" requires a verbatim substring match. It does not cover error/failure behavior when neither text nor domain yields content.

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?

Front-loaded with the core action and cost signal, and every clause carries information. The middle stretches into comma-spliced run-ons (evidence contract and status semantics in one breath), which slightly hurts scanability.

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?

With no output schema, the description steps in to describe the returned object fields and the meaning of found/inferred/not_established, which is exactly what an agent needs to interpret results. Only failure modes and any limits on repeated calls are left unstated.

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% (baseline 3), and the description still adds meaning: `text` skips fetching and is the cheap path, `domain` triggers a homepage fetch only when text is absent, and `labels` are candidates to be tested rather than assignments. That clarifies the cost/behavior tradeoff between the two input paths.

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?

Specific verb+resource: classify a company row against a list of candidate labels, with the outcome shape described. It also positions itself relative to research_row ("Same evidence contract as research_row"), so an agent can tell how the two relate.

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 path selection: pass `text` directly for the cheapest no-fetch route, or use `entity.domain` to trigger a homepage fetch. It also names the dominant use case (tagging a list by industry, ICP fit). It stops short of explicit when-not-to-use exclusions versus research_row.

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.