Teddit

Add a competitor

add_competitor

Start tracking a competitor of a site and return it with its id. The domain lets their pages be recognised among cited sources; aliases are other spellings of the name. Every stored answer is re-read at once (free), so past answers count it too. Brands worth adding are suggested by list_competitors.

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>",
      "name": "<name>"
    },
    "name": "add_competitor"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	The competitor’s name as answers spell it.
`domain`	No	Their site, e.g. "rival.com".
`aliases`	No	Other spellings of the name.
`projectId`	Yes	The project id, from list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Beyond readOnlyHint=false and destructiveHint=false, the description discloses a genuinely nonobvious side effect: every stored answer is re-read at once at no cost, so past answers retroactively include the new competitor. It does not cover duplicate handling or what happens if the same competitor is added twice.

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?

Four short sentences, front-loaded with the action and return value, then parameters, then side effect, then the sibling pointer. Only the parenthetical "(free)" and the slightly compressed re-read sentence cost it a point.

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 create tool with no output schema, the description covers what is returned (the entity plus its id), what the optional fields accomplish, and the retroactive effect on stored answers. Duplicate/conflict behavior is the main omission.

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 already 100%, yet the description adds meaning the schema does not: the domain is what makes the competitor's pages recognizable among cited sources, and aliases are alternate spellings. These are semantic consequences, not restatements of field text.

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?

"Start tracking a competitor of a site and return it with its id" is a specific verb plus resource with an explicit return value. It also distinguishes itself from the sibling list_competitors, which is named as the source of suggestions rather than the place to add.

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?

The closing sentence routes the agent to list_competitors to find candidates worth adding, establishing an implicit discover-then-add workflow. It never states when not to use it (e.g. when a competitor already exists, use 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.

All Teddit tools Inspect

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

Need Help?