Skip to main content
Glama

Quote search-table enrichment

spur_estimate_table_column
Read-onlyIdempotent

Estimate a contacts column for selected/all loaded rows, with optional conditions and provider order. Free; skipped rows and maximum credits are returned.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "table_id": "<table_id>"
    },
    "name": "spur_estimate_table_column"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNo
columnNocontacts
row_idsNo
table_idYes
conditionNo
providersNo
retry_noneNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds real value beyond them: the call is free (no credit spend), and the result reports skipped rows and maximum credits. It does not explain what 'maximum credits' means precisely or whether the estimate is a hard cap, but the cost behavior is disclosed where annotations are silent.

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?

Two compact sentences with the core action front-loaded and the cost/return facts trailing, no filler. The phrasing 'estimate a contacts column' is slightly compressed and takes a second read to parse.

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

Completeness3/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 does partly describe the return (skipped rows, maximum credits), which is the right instinct. For a 7-parameter, zero-coverage tool it still leaves retry_none and the condition shape entirely opaque, and never states its relationship to the paid run tool.

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 0% across 7 parameters, so the description must carry the load. It maps 'selected/all loaded rows' to all/row_ids, 'optional conditions' to condition, and 'provider order' to providers, which is useful, but it never explains retry_none, the condition object's key/op/path/label/value structure, or the mutual behavior of all versus row_ids.

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 names a specific action and resource: estimating a 'contacts' column over selected or all loaded rows, with conditions and provider order. That contrasts meaningfully with the sibling spur_run_table_column, since 'Estimate' plus 'Free' signals a dry-run/cost quote rather than an execution, even though the sibling is never named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: a free estimate logically precedes a paid run, so an agent can infer it should be called before committing credits. There is no explicit when-to-use/when-not statement, no mention of prerequisites, and no named alternative for actually performing the enrichment.

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.

Resources