Skip to main content
Glama

Run the AI visibility check

visibility_run

Ask 10 buyer questions on every engine, 4 runs each, in the background (about 10 minutes); call visibility afterwards. The first check is the baseline, day 0 on the proof page, and is free. After that a re-check costs $2.80 from the balance, at most one a day, charged only when an engine answers. State the price and wait for a yes before a re-check.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "visibility_run"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations only say the tool is not read-only, reaches outside, and is not destructive. The description adds the facts that matter for consent: a background run of about 10 minutes, a free baseline, a $2.80 charge, the limit of one re-check per day, and charging 'only when an engine answers'. It does not say how to tell success from failure, but it gives enough detail for the agent to decide whether to charge the user.

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 puts the action and its duration first, then the cost, and finally the explicit consent rule, so the most important promise comes first. It is dense: the opening clause runs long, and the pricing rules are compressed into semicolons, which makes it slightly harder to scan.

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?

Because it starts an asynchronous job and has no output schema, the agent needs to know both the timing and the handoff, and the description supplies both. It does not say what the agent should do if the background run fails or is still pending, which is a gap for a long-running task.

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?

With zero parameters, there is nothing for the description to disambiguate, so the baseline score applies. The description does not take on that job, but nothing is missing either.

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 concrete action and scope: 'Ask 10 buyer questions on every engine, 4 runs each, in the background'. That is a specific verb-plus-resource, and the follow-up instruction to 'call visibility afterwards' separates this kickoff tool from the sibling that returns results.

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?

Gives clear when-to-use conditions, including the exact sequencing ('call visibility afterwards') and the daily limit of one re-check. It does not spell out when a re-check is unnecessary or what to do if a run fails, so it falls just short of the top score.

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