Skip to main content
Glama

Visibility Genies

Quote a competitor refresh

quote_competitor_refresh

Create a saved quote without provider calls. Returns exact components, limits, payer, setup exclusions, expiry and confirmation hash. Absent competitorIds uses Tracking; explicit [] stays empty. promptIds are required and [] buys no AI answers. Watch quotes cover full future refreshes even if caches are fresh; the Owner approves a watch on the Competitors page. Show the entire quote and paying account to the user before confirmation.

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>",
      "promptIds": "<promptIds>"
    },
    "name": "quote_competitor_refresh"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNorefresh
marketNo
projectIdYes
promptIdsYes
competitorIdsNo

Output Schema

NameRequiredDescriptionDefault
metaNo
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations by stating that no provider calls occur, describing exact quote contents including expiry and confirmation hash, and explaining watch-quote scope and Owner approval. These are substantive behavioral details an agent needs before invoking it.

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 description is dense and front-loaded with the core action and return behavior. Most sentences carry specific operational value, though the packing of defaults, watch behavior, and user-confirmation instructions into one paragraph reduces scannability.

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?

Given that an output schema exists, the description wisely focuses on behavior rather than return-shape details. It covers the critical quote semantics, watch approval, confirmation hash, and array defaults, though the optional market parameter remains unexplained.

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 description coverage, the description usefully explains competitorIds default behavior, explicit [] semantics, promptIds being required, and [] buying no AI answers. However, it leaves market (including locationCode/languageCode) and projectId undocumented, so it does not fully compensate for the missing schema descriptions.

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: 'Create a saved quote' with the key qualifier 'without provider calls'. This clearly distinguishes it from execution/confirmation siblings such as confirm_competitor_refresh and execute_competitor_refresh.

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?

The description makes the quote-before-confirmation workflow clear and warns to show the entire quote and paying account before confirmation. It does not explicitly name confirm/execute alternatives, but the context is sufficiently clear for correct use.

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