Skip to main content
Glama
ayrank-tools

ayrank-tools

Official
by ay-automate

AI answer tracking: what exists

ayrank_tracking_info
Read-only

Locate where to track whether AI assistants name or cite a brand. It returns the paid AY Rank app/MCP server and a free one-off check, with no network call.

Instructions

Use when someone asks to track whether ChatGPT, Perplexity, Gemini, Claude or Google AI answers name or cite a brand. This server cannot do that: the free AY Rank API never asks any AI assistant anything. This tool returns where tracking does exist (the paid AY Rank app and its own MCP server) and the free one-off check. Makes no network call.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds non-derivable behavior: the free AY Rank API never queries any AI assistant, and this tool makes no network call, which prevents the agent from treating the output as live tracking data. It does not describe output shape, though the payload is a static pointer list.

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?

Three sentences, front-loaded with the trigger, then the limitation, then the payload. No filler. The double negation ('cannot do that ... never asks') is a little dense but each sentence carries a distinct fact.

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?

For a no-parameter, no-output-schema informational tool, the description covers trigger, limitation, and what the response points to. The only gap is that it does not name the paid app or free check explicitly, so the agent learns the destination only after calling.

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?

The tool takes zero parameters, so the baseline of 4 applies. The description correctly implies a parameterless, static lookup and does not invent inputs that the empty schema contradicts.

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?

The description gives a concrete verb and object: it returns where AI-answer tracking does exist (paid AY Rank app / its MCP server, plus a free one-off check). It also explicitly rules out the naive reading of the name by stating the free API never asks any AI assistant anything. It is slightly circular for a 'what exists' pointer tool, but an agent can still tell what it will get back.

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?

It opens with an explicit trigger ('Use when someone asks to track whether ChatGPT, Perplexity, Gemini, Claude or Google AI answers name or cite a brand') and immediately states the negative case ('This server cannot do that'). It then redirects to where the capability actually lives, which is exactly the routing guidance an agent needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.