Skip to main content
Glama

Property DNC status

spur_get_property_dnc
Read-onlyIdempotent

Stored per-number DNC result, blocked state, provider, check date and expiry. Free; requires the account's restricted-contact permission. A clear DNC check does not establish consent to text.

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_get_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 establish read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower; the description still adds real context — no cost, a restricted-contact permission prerequisite, and an interpretive caveat that a clear DNC does not equal consent to contact. It doesn't say what happens when no stored result exists, which is the main remaining gap.

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 compact sentences, front-loaded with the returned data and followed by cost/permission and a caveat; nothing is wasted. It could be tightened slightly by merging the cost and permission notes, but it is well structured.

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 read-only getter with no output schema and full annotation coverage, the description supplies cost, permission, and interpretive context. The only meaningful omissions are the behavior when no prior check exists and how it differs operationally from the check/plan siblings.

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% for the single property_id parameter, so the description must compensate. 'Per-number' hints that results are keyed to phone numbers, but it never explains what property_id identifies or its expected format, so it adds only marginal meaning over the bare 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?

The description names the specific resource and its returned fields (per-number DNC result, blocked state, provider, check date, expiry), and the word 'Stored' signals this is a read of a cached result rather than a live check. It stops short of a clear verb or explicitly naming spur_check_property_dnc / spur_plan_property_dnc as the contrasting tools, so sibling differentiation is only implied.

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 hinted rather than stated: 'Stored' and 'Free' imply you call this to read an existing result instead of paying for a fresh check, and the closing caveat warns against treating a clear result as consent. There is no explicit when-to-use/when-not-to-use statement or named alternative, leaving the agent to infer the routing against spur_check_property_dnc.

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