Skip to main content
Glama

Visibility Genies

Read competitor refresh progress

read_competitor_refresh
Read-only

Read saved component outcomes, actual spend, payer and safe continuation state. Does not execute or buy anything.

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

Input Schema

NameRequiredDescriptionDefault
idYes
projectIdYes

Output Schema

NameRequiredDescriptionDefault
metaNo
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false; the description adds only the 'does not buy anything' no-cost reassurance, which extends slightly beyond readOnly. It says nothing about pagination, freshness, or what happens when no refresh exists.

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?

Two tight sentences, front-loaded with what is read and closed with the safety constraint. Slightly dense jargon ('payer and safe continuation state') costs a point but nothing is wasted.

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 no explanation, and the read-only annotations cover safety. However, for a two-required-parameter tool with zero schema description coverage, the definition leaves the identity of the 'id' parameter completely unexplained, which is a real gap before invocation.

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?

Schema description coverage is 0% and the description never mentions either parameter. 'id' and 'projectId' are both required, and it is ambiguous whether 'id' is a refresh job id, a competitor id, or something else; the description does nothing to resolve that.

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 a concrete list of resources returned: saved component outcomes, actual spend, payer, and continuation state. It reads as a state/progress inspection for a competitor refresh, though it never names the sibling tools (read_saved_result, confirm_competitor_refresh) it must be distinguished from.

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?

'Does not execute or buy anything' implicitly routes the agent away from execute_competitor_refresh and toward this as the safe inspection step, but there is no explicit when-to-use statement, no prerequisite mention, and no named alternative, so the guidance is inferred rather than 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