Skip to main content
Glama

Update competitor

update-competitor
Destructive

Change a competitor's display name or aliases, then relabel the domain's prompts. These names decide which AI answers count as a mention; its domain name only counts when it matches the display name. aliases replaces the whole list. competitor_id comes from 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": {
      "competitor_id": "<competitor_id>"
    },
    "name": "update-competitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
aliasesNoFull alias list; replaces the current one
display_nameNoNew display name
competitor_idYesCompetitor ID from list-competitors

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / aliases / description
      Previous value: -"Brand aliases"New value: +"Full alias list; replaces the current one"
    • 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.5/5.0
Behavior5/5

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

Goes well beyond the destructiveHint annotation: it discloses the cascading side effect on the domain's prompts, states that 'aliases replaces the whole list' (i.e. what gets overwritten), and explains the matching rule that makes the display name operationally significant. This is exactly the kind of 'what actually changes' context 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the mutation and its cascade in the first sentence, followed by justification and constraint notes. Dense but every clause carries information; nothing is padding, though the semicolon-joined middle sentence takes a second read.

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 mutation with no output schema, it covers the mutation, the cascade, the overwrite semantics and the ID source. It leaves undeclared what happens if both optional fields are omitted, whether prompt relabeling is immediate or reversible, and what the response returns.

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%, so the baseline is 3; the description still adds value by explaining that the names determine what counts as a mention and that the domain name only counts when it matches the display name. The replacement semantics for aliases largely restate the schema description, so it lands just above 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 plus the exact fields ('Change a competitor's display name or aliases') and, crucially, a downstream effect not visible from the name ('then relabel the domain's prompts'). The verb distinguishes it cleanly from add-competitor, delete-competitor and list-competitors without needing to name them.

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 the agent at list-competitors for the required competitor_id and explains the semantic consequence of the values (which AI answers count as mentions). It gives clear context for when to call it, but stops short of explicit exclusions such as 'use add-competitor to create a new one instead'.

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