pricing_infoFree — list every paid tool in the 'seo-tools' bundle with its price, payTo address and network. Call this first if you don't have a wallet ready yet.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare read-only and non-destructive behavior. The description adds the 'Free' aspect and clarifies that no wallet is needed, which provides useful extra context beyond the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is one sentence, front-loaded with 'Free', and every word contributes meaning. It avoids redundancy and maintains high clarity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a parameterless tool with no output schema, the description fully explains what it returns and when to use it. It is complete for the tool's simplicity and context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are zero parameters, so schema coverage is 100% by default. The description adds no parameter info, which is appropriate; no parameters means the baseline of 4 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists every paid tool in the 'seo-tools' bundle with price, payTo address, and network. This specific verb+resource+output distinguishes it from sibling tools that perform audit/checker functions.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly instructs to call this first if a wallet isn't ready, providing a clear usage context. It does not mention alternatives or when not to use it, but the single-sentence guidance is sufficient for a simple tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tools have overlapping purposes: ai-crawler-access-checker and llms-txt-auditor both check robots.txt for AI crawler access, while ai-answer-change-alert, ai-overview-tracker, and llm-brand-visibility all track AI-generated citations/visibility. An agent may struggle to pick the right one without reading full descriptions.
Most tools use lowercase hyphenated noun phrases (e.g., ai-answer-change-alert, social-preview-checker), but pricing_info uses an underscore, breaking the otherwise consistent pattern. Minor deviation but still readable.
Seven tools is well-scoped for a specialized SEO/AI-visibility server. Each tool addresses a distinct aspect (crawler access, llms.txt, AI citations, brand visibility, social previews) without being excessive, and the pricing_info helper is a sensible addition.
The set covers the core AI-era SEO workflow: audit AI crawler access, validate llms.txt, track AI overview citations, monitor answer changes, and check brand visibility. Missing obvious features like generating llms.txt or deeper competitor analysis, but no critical dead ends.