Skip to main content
Glama

Visibility Genies

Save a competitor

save_competitor

Add or edit a competitor, aliases, notes and status. New manual rivals default to Tracking. Maximum ten tracked rivals for new additions; existing longer lists remain intact. Confirm a name-only suggestion's real domain before saving with status tracking. Explicit comparison selections always override these defaults. Use expectedRevision from read_competitors for edits.

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": "save_competitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
nameNo
notesNo
domainNo
statusNo
aliasesNo
projectIdYes
capitalOnlyNo
expectedRevisionNo

Output Schema

NameRequiredDescriptionDefault
metaNo
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the mutation profile is covered structurally. The description adds real value beyond that: default status assignment, the ten-rival ceiling with grandfathering of existing lists, and optimistic-concurrency via expectedRevision. It does not say what happens when the cap is hit or how a revision conflict surfaces, leaving the failure behavior opaque.

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?

Tight, front-loaded sentences with no filler; the core action comes first and constraints follow. The clause "Explicit comparison selections always override these defaults" is cryptic shorthand that costs a re-read, which is the main structural weakness.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained. For a nine-parameter mutation with zero schema description coverage, the description covers defaults, limits and concurrency but leaves several parameters and the enum semantics undocumented, so an agent still has to guess on capitalOnly and projectId.

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 0% across nine parameters, so the description must carry the load and only partly does: it covers aliases, notes, status, expectedRevision, name and domain implicitly. capitalOnly, projectId, and the meaning of the id field for edits are never explained, and the status enum values beyond the 'tracking' default are undefined.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Add or edit a competitor, aliases, notes and status") and makes the create-vs-edit duality explicit. It does not name the plural sibling save_competitors to route bulk operations, so differentiation is implied rather than stated.

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 concrete operating rules: manual rivals default to Tracking, a ten-tracked-rival cap with existing longer lists grandfathered, and a directive to confirm a name-only suggestion's real domain before saving as tracking. It also names read_competitors as the source of expectedRevision. It lacks an explicit when-to-use-this-vs-another-save-tool statement, which keeps it off a 5.

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