Skip to main content
Glama

Archive (delete) a Gambit

archive_gambit
DestructiveIdempotent

Archive (delete) one of YOUR Gambits (requires api:account) — the call for "delete my GOOGL Gambit" (find the case_id with list_gambits). The Gambit leaves your Gambits and Gambit stops sending you updates on it. It is a soft delete: restore_gambit brings it back for 3 days, then it is purged for good with its history. list_gambits with archived=true lists archived Gambits with purge_at. Safe to repeat: archiving an archived Gambit changes nothing. One that is not yours answers 404. Returns the Gambit (state archived, archived_at, purge_at). Confirm with the user before archiving a Gambit. This places no order. The response carries app_url, the Tracking screen.

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": {
      "case_id": "<case_id>"
    },
    "name": "archive_gambit"
  }
}

Input Schema

NameRequiredDescriptionDefault
case_idYesa Gambit id from list_gambits (UUID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds substantial context the annotations cannot: soft-delete semantics, a 3-day restore window, permanent purge of history afterward, 404 for Gambits not owned, no-op on repeat archiving, and a reassurance that no order is placed. It also discloses the response shape (state, archived_at, purge_at) despite having no output schema.

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?

Front-loaded with the action and scope, then progressively narrower detail (soft delete, idempotency, error case, return value, confirmation). It is a single dense paragraph; a mild redundancy exists between 'Archive (delete)' and the quoted 'delete my GOOGL Gambit' framing, but no sentence is filler.

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 one-parameter destructive mutation with no output schema, the description covers authorization (api:account), reversibility window, permanent consequences, idempotency, error behavior, confirmation requirement, and returned fields. Nothing an agent needs in order to call it safely is missing.

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% and there is only one required parameter, so the schema already carries the format (UUID). The description still adds provenance value by telling the agent where to obtain case_id (list_gambits), which the schema only states tersely.

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 ('Archive (delete) one of YOUR Gambits') and pins the scope to the caller's own Gambits, which distinguishes it from read-oriented siblings like get_gambit. It also gives a concrete user-utterance mapping ('the call for "delete my GOOGL Gambit"'), so an agent can match intent without opening a schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: find the case_id via list_gambits, and use restore_gambit if the intent is to undo, plus a mandatory confirmation step before archiving. It also names the follow-up query (list_gambits with archived=true) for inspecting purged-pending items, so both the entry and exit paths are covered.

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