Skip to main content
Glama

Preview DNC checks

spur_plan_property_dnc
Read-onlyIdempotent

Quote checks for unchecked or expired numbers. Free. Show the credits before calling spur_check_property_dnc.

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>"
    },
    "name": "spur_plan_property_dnc"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond that with 'Free' (no credit consumption) and the fact that the call yields a credit quote rather than a consumed operation — exactly the behavioral detail an agent needs before a paid follow-up.

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?

Three short sentences with no waste, and the free/cost point is front and center. The final sentence is the operational instruction, placed after the purpose, which keeps it front-loaded overall.

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?

For a one-parameter preview tool with no output schema, the definition covers purpose, cost, and the recommended call sequence, and 'Show the credits' hints at the return value. The remaining gap is the meaning of 'unchecked or expired' and the per-property scoping of the quote.

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?

Schema description coverage is 0% and the single required parameter property_id is undocumented in the schema. The description never mentions that the quote is scoped to a property, so it does not compensate for the coverage gap; only the self-evident parameter name carries meaning.

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 uses the verb 'Quote' against the resource of DNC 'checks for unchecked or expired numbers', and the title frames it as a preview. Together with the explicit reference to spur_check_property_dnc, an agent can tell this is a cost-estimate step rather than the actual check, though 'Quote' alone is slightly jargon-y.

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?

It states the ordering explicitly: call this to show credits before calling spur_check_property_dnc, and notes it is free. It gives a clear context for use but does not state any exclusion case (e.g., when to skip the preview and call the check directly).

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