Skip to main content
Glama

Enrich search-table contacts

spur_run_table_column
Destructive

Start the approved contacts column as a background run under a credit ceiling. Saves rows for free, then enriches; poll with spur_control_table_run action=get.

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>",
      "credit_limit": "<credit_limit>",
      "confirm": "<confirm>"
    },
    "name": "spur_run_table_column"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNo
columnNocontacts
confirmYesSet to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.
row_idsNo
table_idYes
conditionNo
providersNo
retry_noneNo
credit_limitYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

The annotations already disclose the destructive, open-world, non-idempotent profile, and the description usefully adds that this is asynchronous, consumes credits up to a ceiling, saves rows for free before enrichment, and requires polling. It does not specify what existing data may be overwritten or whether the run can be cancelled or undone, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action and constraints, then the polling follow-up. There is no filler, and each clause adds useful operational information.

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

Completeness2/5

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

For a destructive, open-world background run with nine parameters and no output schema, the description omits most parameter semantics, approval mechanics beyond the word 'approved', and cancellation or error behavior. It covers the high-level lifecycle and polling but not enough to safely invoke all available options.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With nine parameters and only 11% schema description coverage, the description adds meaning only for credit_limit (ceiling), confirm ('approved'), and column ('contacts'). It leaves table_id, row_ids, condition, providers, all, and retry_none unexplained, so it does not compensate for the very low schema coverage.

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?

States a specific action (start as a background run) on a specific resource (the approved contacts column), including the credit-ceiling constraint and polling follow-up. It names spur_control_table_run for polling but does not distinguish itself from siblings such as spur_estimate_table_column, so it falls short of a 5.

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?

Implies the tool is used after approval ('approved', plus the confirm parameter) and when a background enrichment should run under a ceiling, and it tells the agent to poll via spur_control_table_run. It does not explain when to prefer this over estimation or other table-run tools, nor does it state exclusions.

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