Skip to main content
Glama

Check property phone numbers against DNC

spur_check_property_dnc
Destructive

Run approved DNC checks with the quoted credit ceiling. Retains suppression and partial results if a provider fails. Requires approval of the quote.

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": {
      "property_id": "<property_id>",
      "max_credits": "<max_credits>",
      "confirm": "<confirm>"
    },
    "name": "spur_check_property_dnc"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesSet to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.
max_creditsYes
property_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructive=true, openWorld=true and non-idempotent, so the safety bar is partly covered. The description goes beyond them by disclosing that credits are consumed up to the quoted ceiling, that suppression and partial results are retained on provider failure, and that user approval of the quote is mandatory — exactly the operational context an agent needs before a spend action.

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?

Three short sentences with no waste; the approval requirement and the credit ceiling, the two facts that most affect correct invocation, are front-loaded.

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?

For a destructive, credit-spending, non-idempotent tool with no output schema, the description covers cost, partial-failure behavior and approval. It still omits what one check corresponds to (per number vs per property), whether re-running wastes credits, and what is returned, which matters given the missing output schema.

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 33%: only 'confirm' is documented in the schema. The description links 'quoted credit ceiling' to max_credits, implying it should match the quote, which is meaningful added meaning, but property_id remains undocumented in both places and the confirm flag's semantics are already fully spelled out in 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?

Names a specific verb and resource: running DNC checks on a property's phone numbers, plus the credit ceiling framing. It is distinguishable from planning and retrieval siblings by the word 'approved', though it never names an alternative explicitly.

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?

'Run approved DNC checks' and 'Requires approval of the quote' imply this is the execution step that follows a quote/plan, which is useful implied sequencing. However, no sibling is named and there is no explicit when-not guidance, so the agent must infer that spur_plan_property_dnc precedes this.

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