Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Estimate AI visibility cost

seo_estimate_ai_visibility_cost
Read-onlyIdempotent

Estimate one scheduled check, one-off check, and the monthly cost of a daily, weekly, or monthly schedule without collecting answers. Optional patch estimates proposed settings; promptIds estimates a check of those prompts. costUsd prices each scheduled check. runNowCostUsd prices a one-off check, which collects live answers within minutes at a higher price. Show the customer the relevant cost before enabling tracking or running a paid check, and pass the approved runNowCostUsd to seo.run_ai_visibility_check as maxCostUsd.

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": {
      "siteId": "<siteId>"
    },
    "name": "seo_estimate_ai_visibility_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
patchNoOptional proposed changes to estimate before saving.
siteIdYesThe Sextant site ID.
promptIdsNo
scheduleIntervalNoCadence for the monthly cost estimate. Defaults to the saved schedule, or weekly.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description still adds the key behavioral fact that it estimates 'without collecting answers', and that runNowCostUsd involves live collection within minutes at a higher price. It does not mention rate limits or auth requirements, which keeps it short of a 5.

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?

Front-loaded with what is returned, then parameter roles, then the workflow instruction - a sensible order with no filler. Several clauses are packed into long sentences, but each one carries distinct information an agent needs.

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?

There is no output schema, and the description compensates by explaining the returned figures (costUsd per scheduled check, runNowCostUsd for a one-off live check) and their relative pricing. Combined with the handoff to run_ai_visibility_check, an agent can complete the estimate-then-approve loop without further discovery.

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 coverage is 75%, yet the description still clarifies the semantic role of two ambiguous parameters: patch means 'proposed settings' to estimate before saving, and promptIds means estimate a check scoped to those prompts. scheduleInterval's meaning is carried by the opening sentence about daily/weekly/monthly cadence. siteId is left to the schema.

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 (Estimate) and resource (cost of one scheduled check, a one-off check, and monthly cadence-based cost), and separates itself from seo_estimate_rank_tracker_cost by naming AI visibility checks and prompts explicitly. An agent reading only the first sentence knows exactly what is priced.

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?

Gives an explicit call moment ('before enabling tracking or running a paid check') and a concrete downstream handoff ('pass the approved runNowCostUsd to seo.run_ai_visibility_check as maxCostUsd'). The alternative path - the paid check itself - is named with the condition that selects it.

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