Skip to main content
Glama

Visibility Genies

Approve a competitor quote

confirm_competitor_refresh

Only call after the user approves this exact quote, payer and price. Submit its unmodified id and confirmationHash. Refresh confirmation records approval; execute_competitor_refresh starts one component. A monthly watch cannot be confirmed here: it buys every 30 days only under the Owner's approval, which they give on the Competitors page, so show the user the watch quote and send them there. Changed or expired quotes require a fresh quote and approval.

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

Input Schema

NameRequiredDescriptionDefault
idYes
kindNorefresh
projectIdYes
confirmationHashYes

Output Schema

NameRequiredDescriptionDefault
metaNo
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (non-read-only, non-destructive, closed-world), the description adds real behavioral context: the confirmation is tied to an unmodified quote id and hash, and changed or expired quotes are rejected and require a fresh quote and approval. It does not describe what the confirmation record contains or what state changes afterward, though an output schema partially covers returns.

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?

The critical safety precondition is front-loaded and no sentence is filler. However, 'Refresh confirmation records approval; execute_competitor_refresh starts one component' is compressed into a cryptic clause, and the mention of 'payer and price' (not schema parameters) could briefly puzzle the reader.

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?

This is a consequential multi-step action (quote → user approval → confirm with hash), and the description covers the prerequisite, the hash-binding requirement, the expiry failure mode, and the excluded watch case. The main remaining gap is the unexplained projectId parameter; return values are covered by the output schema.

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?

With 0% schema coverage and four parameters, the description compensates partially: it says the id and confirmationHash must be submitted unmodified and bound to a user-approved quote, and it implicitly explains the kind enum by excluding 'watch'. It says nothing about projectId or the default 'refresh' value, leaving one parameter fully undocumented.

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 makes clear this tool confirms/records approval for an already-quoted competitor refresh, sending an id plus confirmationHash. It distinguishes itself from execute_competitor_refresh ('starts one component'), but the core verb+resource statement is telegraphed through clauses rather than stated up front.

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

Usage Guidelines5/5

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

Explicit gating condition (only after the user approves this exact quote, payer and price), an explicit alternative (execute_competitor_refresh starts the work), and an explicit exclusion (a monthly watch cannot be confirmed here; direct the user to the Competitors page for Owner approval). Both when-to-use and when-not-to-use are stated.

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