Skip to main content
Glama

Take a spec down

unpublish_spec
Destructive

Takes one of the signed-in person's specs off Spekkr: its page, its files and its place in search. The versions it had stay used up, so publishing it again needs a higher version. This tool needs sign-in. Ask the person before you call it.

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": {
      "id": "<id>"
    },
    "name": "unpublish_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe spec's id, like username/name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by specifying what is destroyed (page, files, search presence), the irreversible side effect (versions stay consumed so republishing needs a higher version), and the auth and human-confirmation requirements. The destructiveHint annotation is confirmed and enriched rather than merely restated.

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 short sentences: purpose first, then the lasting consequence, then the operational constraints. No filler and nothing buried.

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 single-parameter, no-output-schema destructive tool, the description supplies everything needed: scope of removal, irreversibility, auth, and consent. Nothing required to call it correctly is missing.

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 coverage is 100% and the single 'id' parameter carries its own format example (username/name), so the schema does the heavy lifting. The description adds no further meaning about the id, making the baseline 3 appropriate.

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 ('takes ... specs off Spekkr') and enumerates exactly what is removed: the page, the files, and search placement. It also implicitly contrasts with publish_spec by noting that republishing requires a higher version, so an agent can distinguish the take-down action from its sibling.

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 precondition ('needs sign-in') and an explicit consent rule ('Ask the person before you call it'), which is strong operational guidance for a destructive action. It stops short of naming alternatives or when-not-to-use conditions beyond that consent gate.

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