cargoshipper-mcp

by scarr7981

Overview Schema Source Related Servers Discussions Admin

Python

Local

cf_purge_cache

Purge CloudFlare cache for a specified zone, including all cache, specific files, tags, or hostnames.

Instructions

Purge CloudFlare cache

Args: zone_id: CloudFlare zone ID purge_everything: Purge all cache (use carefully) files: List of specific URLs to purge tags: List of cache tags to purge hosts: List of hostnames to purge

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": {
      "zone_id": "<zone_id>"
    },
    "name": "cf_purge_cache"
  }
}

Input Schema

Name	Required	Description	Default
`zone_id`	Yes
`purge_everything`	No
`files`	No
`tags`	No
`hosts`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 26, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only says 'use carefully' for purge_everything, hinting at destructiveness, but fails to mention rate limits, idempotency, or effects on other Cloudflare actions. This is insufficient.

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?

The description is concise: two sentences plus a bullet list. The main action is front-loaded. The 'Args' format is clear but slightly informal; still effective.

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?

An output schema exists, so return values are covered. However, the description lacks explanation of how each purge method works (e.g., purge_everything invalidates all cache, files/tags/hosts are selective) and does not provide enough context for an agent to choose correctly.

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

Parameters4/5

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

Schema description coverage is 0%, so the description carries the burden. It adds meaning beyond the schema: e.g., 'files: List of specific URLs to purge,' 'tags: List of cache tags to purge,' and 'purge_everything: Purge all cache (use carefully).' This clarifies each parameter's role, though it could be more detailed.

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 starts with 'Purge CloudFlare cache', which clearly states the verb (purge) and resource (CloudFlare cache). Among sibling tools like cf_create_dns_record, cf_get_analytics, etc., none are cache-related, so it effectively distinguishes itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool vs alternatives, nor does it explain when to choose purge_everything over files/tags/hosts. The only hint is 'use carefully' for purge_everything, but there are no explicit use cases or exclusions compared to sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.