Skip to main content
Glama
Sign In

Squish

by co.squish
OverviewDiscussionsAdmin

Purge my cdn cache

purge_my_cdn_cache

Clears the CDN edge cache for one of the customer's hosting sites so visitors get the latest files right away. Use after they changed their site and still see the old version. Two-step: (1) call with confirm:false for the preview, ask for a yes; (2) ONLY after an explicit yes in their most recent message, call with confirm:true. Harmless to the site (the next visit refills the cache), scoped to this domain only.

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": {
      "domain": "<domain>"
    },
    "name": "purge_my_cdn_cache"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe hosted site's domain.
confirmNofalse (default) returns the preview; true purges. Pass true ONLY after explicit user confirmation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Adds substantive behavior beyond the annotations: a required preview-then-confirm sequence, the 'most recent message' consent rule, and reassurance that the purge is non-destructive because the cache refills on next visit — consistent with destructiveHint=false. It does not mention rate limits, cooldowns, or what the preview output contains.

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 sentences, all front-loaded: purpose, trigger, then the confirm protocol. Nothing is repeated and no sentence could be dropped without losing a constraint the agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation tool with annotations already covering the safety profile, this covers trigger, scope, consent protocol, and post-call state. No output schema is needed since the description frames the preview/final call structure itself.

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 coverage is 100%, so both parameters are already documented; the description reinforces the confirm=false/true distinction and adds the sequencing constraint the schema only hints at. The 'domain' parameter gets only the scoping phrase 'this domain only', adding little to the schema's own wording.

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?

States a specific verb and resource ('Clears the CDN edge cache') plus explicit scope ('for one of the customer's hosting sites', 'scoped to this domain only'), which separates it from account-level siblings like get_my_cdn_stats and set_my_cdn.

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?

Gives a clear trigger condition ('Use after they changed their site and still see the old version') and a mandatory two-step invocation protocol with an explicit consent gate. It stops short of naming alternative tools (e.g. get_my_cdn_stats, set_my_cdn) for adjacent needs, so no true when-not guidance.

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

All Squish toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources