Skip to main content
Glama

Export saved contacts as CSV

spur_export_contacts
Read-onlyIdempotent

Export selected saved properties or one list as CSV. DNC/TCPA-blocked, invalid and disallowed numbers never enter callable Phone columns. Blocked numbers are labeled separately; spreadsheet formulas are escaped. Returns an inline text/csv resource, with pagination for large lists. Makes no provider call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "spur_export_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
list_idNo
property_idsNo
skip_no_callableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (which already declare read-only, idempotent, closed-world), the description discloses substantive behavior: DNC/TCPA-blocked, invalid and disallowed numbers are excluded from callable Phone columns, blocked numbers are labeled separately, spreadsheet formula injection is escaped, output is an inline text/csv resource with pagination, and no provider call/credit consumption occurs. These are exactly the traits an agent cannot infer from the structured fields.

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?

Four sentences, front-loaded with purpose, then safety/filtering behavior, then return format. Dense and largely waste-free; the closing "Makes no provider call" is terse but justifies its place by telling the agent there is no credit cost.

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?

There is no output schema, and the description adequately covers the return shape (inline text/csv resource, pagination) and data-safety filtering. However, for a five-parameter tool with zero schema documentation, the absence of per-parameter semantics leaves a real gap an agent would hit on first call.

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% for five parameters, so the description carries the full burden, yet it never names limit, offset, skip_no_callable, list_id, or property_ids explicitly. Only indirect hints exist ("one list", "pagination for large lists"), leaving the meaning of skip_no_callable and the offset/limit mechanics unstated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ("Export ... saved properties ... as CSV") and defines scope precisely: either a set of selected properties or a single list. An agent can immediately tell this is the CSV export path rather than the enumeration/listing tools.

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 distinguishes the two invocation modes (selected properties vs. one list), which is the key routing decision for this tool. It does not name an alternative tool or state when not to use it, so it falls short of explicit when/when-not guidance.

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