Skip to main content
Glama

Visibility Genies

Stop a competitor watch

cancel_competitor_watch

Cancel future monthly competitor purchases for the saved watch. No provider calls. Already completed purchases remain saved.

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

Input Schema

NameRequiredDescriptionDefault
idYes
projectIdYes

Output Schema

NameRequiredDescriptionDefault
metaNo
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

The description adds behavior beyond the annotations: 'No provider calls' tells the agent no external fetch happens, and 'Already completed purchases remain saved' confirms the operation is partial and consistent with destructiveHint=false. It does not explain whether the call is idempotent or what happens on a second call, but the added context is substantive.

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 with the core action front-loaded and the two qualifiers (no provider calls, completed purchases preserved) following in order of importance. No filler or restatement of the title.

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 described, and the non-destructive semantics are covered. However, for a two-parameter tool with zero schema documentation, leaving both identifiers unexplained is a real gap an agent would notice when constructing the call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both parameters (projectId, id) have 0% schema description coverage, so the description carries the full burden — yet it never explains what either identifier refers to. 'The saved watch' hints that id is a watch identifier, but projectId is completely unexplained and its relationship to the watch is unstated.

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?

The description states a specific verb and object: cancel future monthly competitor purchases for a saved watch. The clause 'Already completed purchases remain saved' clarifies that this is a recurring-purchase cancellation rather than deletion of the watch itself, which implicitly separates it from remove_competitor. It stops short of naming that sibling, so it is clear but not fully differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: an agent can infer this is the right tool when a user wants to stop recurring competitor purchases. There is no explicit when-not guidance, no mention of alternatives like remove_competitor, and no statement about preconditions (e.g., whether the watch must currently be active).

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