Skip to main content
Glama
Sign In

Teddit

by io.teddit
OverviewDiscussionsAdmin

Remove a competitor

remove_competitor
Destructive

Stop tracking a competitor of a site. Stored answers stay and are re-read without it, so it drops out of reports and share of voice. Add it again with add_competitor.

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": {
      "projectId": "<projectId>",
      "competitorId": "<competitorId>"
    },
    "name": "remove_competitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesThe project id, from list_projects.
competitorIdYesThe competitor id, from list_competitors.

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?

Annotations declare destructiveHint=true, and rather than merely repeating that, the description clarifies the blast radius: stored answers are preserved and simply re-read without the competitor. It also confirms reversibility via add_competitor and describes the downstream effect on reports and share of voice — context the annotations cannot convey.

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, front-loaded with the action, followed by consequences and then the reversal path. Every sentence carries distinct information with no restatement of the name or title.

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 destructive tool with full schema coverage and no output schema, the description covers action, data-safety semantics, downstream effects, and recovery. Nothing an agent needs to invoke 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 description coverage is 100% and both parameters already document their source (list_projects, list_competitors), so the schema does the heavy lifting. The description adds no parameter-level detail, which is acceptable given the schema's completeness but earns only the baseline.

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 of a site'), which is unambiguous and immediately separable from siblings like update_competitor or list_competitors. It also names add_competitor as the inverse operation.

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?

Points to add_competitor as the way back, which gives the agent a clear pairing between the two tools. It stops short of stating preconditions, such as whether the competitor needs to exist or whether removal affects in-flight scans, but the usage context is clear.

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

All Teddit 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