Skip to main content
Glama

Visibility Genies

Run a competitor refresh step

execute_competitor_refresh

May spend money. Execute the next component of a previously confirmed quote. Never call without the user's exact approval. Read returned progress before continuing. Do not retry uncertain or unreadable work; use recover_competitor_refresh to reconcile without buying again. Server enforces pinned payer, payload and price. Each call may spend up to the workspace's agent spend limit ($2.00 unless changed in Settings) without asking: it holds at most its estimate plus a margin while it runs and is charged what it bought, never more. A call whose maximum is above the limit is refused before anything is bought, with its estimate and maximum: ask the user, then call again with approvedMaxCostUsd set to the amount they approved.

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

Input Schema

NameRequiredDescriptionDefault
idYes
projectIdYes
approvedMaxCostUsdNoThe most, in USD, the user approved for this call after seeing its estimate and maximum. Only needed after a call was refused for costing more than the workspace's agent spend limit; never set it without asking the user.

Output Schema

NameRequiredDescriptionDefault
costNo
metaNo
resultYes
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes far beyond the annotations: it discloses that the call spends money, that the server pins payer/payload/price, how funds are held (estimate plus margin) and charged (what was bought, never more), and that over-limit calls are refused before purchase with estimate and maximum returned. This is exactly the cost and safety context an agent needs before invoking a paid, open-world tool.

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?

Front-loads the highest-stakes fact ('May spend money') in three words, then layers approval, retry, recovery, and cost mechanics in short imperative sentences. There is minor overlap between 'never call without the user's exact approval' and the later 'ask the user' guidance, but each covers a distinct decision point.

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

Completeness5/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 spelled out, and the description still tells the agent to read returned progress before continuing. Combined with the spend-limit, refusal, and recovery rules, an agent has everything needed to call this paid tool safely.

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 description coverage is only 33%, but the description fully explains the one non-obvious parameter: approvedMaxCostUsd is only needed after a refusal, must equal what the user approved, and must never be set without asking. The remaining projectId and id parameters are not described, but their meaning is evident from naming and the required-parameter contract.

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 ('Execute the next component of a previously confirmed quote'), which pins the tool to one step of a multi-step refresh flow. It implicitly distinguishes itself from the quote/confirm/recover siblings by making clear the quote is already confirmed and that recovery is a separate tool.

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?

Explicitly names the precondition (user's exact approval), the prohibition (never retry uncertain or unreadable work), and the alternative for that case (recover_competitor_refresh to reconcile without buying again). It also gives the exact recovery path when a call is refused: ask the user, then re-call with approvedMaxCostUsd.

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