Skip to main content
Glama

Delete competitor

delete-competitor
Destructive

Stop tracking a competitor on its domain. Its past results stay in completed runs; future runs no longer score it, and the domain's prompts are relabelled. competitor_id comes from list-competitors. Confirm with the user first.

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": {
      "competitor_id": "<competitor_id>"
    },
    "name": "delete-competitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
competitor_idYesCompetitor ID from list-competitors

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / competitor_id / description
      Previous value: -"Competitor ID"New value: +"Competitor ID from list-competitors"
  2. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / competitor_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description goes well beyond them by defining the blast radius: past results in completed runs are retained, future runs simply stop scoring the domain, and the domain's prompts are relabelled. That resolves the main ambiguity an agent would have (is this a hard delete?) and adds a human-confirmation requirement, which is real context the annotations cannot express.

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, zero filler, with the core action front-loaded and the consequential side effects and confirmation requirement following in order of importance. Every clause carries information the agent needs.

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

Completeness4/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 the important ground: what happens, what survives, and that confirmation is required. It stops short of saying what the call returns on success or whether the competitor can be re-added afterwards, which would round out the picture.

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 description coverage is 100% and the single parameter already documents itself as the ID from list-competitors, so the description's 'competitor_id comes from list-competitors' is a near-verbatim repeat. Baseline 3 is appropriate; no extra meaning is added.

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 ('Stop tracking a competitor on its domain') and immediately clarifies the semantics of 'delete' here — a soft stop, not a purge. This clearly separates it from add-competitor and update-competitor without requiring the agent to open another schema.

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 the prerequisite ('competitor_id comes from list-competitors') and an explicit procedural rule ('Confirm with the user first'), which is exactly the guardrail needed for a destructive operation. It does not name an alternative for the related-but-different case (e.g. rename via update-competitor), so it falls short of a full when/when-not pair.

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