Skip to main content
Glama
Sign In

SEO Score API

by io.github.SeoScoreAPI
OverviewDiscussionsAdmin

One-off AI Citation Check

citation_check
Read-onlyIdempotent

One-off AI citation check for a brand and one prompt: no tracker, metered per check (one check per engine per sample). Paid plans only (Starter and up).

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": {
      "brand": "<brand>",
      "prompt": "<prompt>"
    },
    "name": "citation_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandYesBrand to look for in the answers, e.g. Acme.
promptYesThe question a buyer would ask an AI assistant.
domainsNoThe brand's domains, to count citations of them.
enginesNoDefault: gpt, gemini, perplexity, claude. gpt answers from the model's own knowledge (no browsing); chatgpt is the web-search product and needs an OpenAI key on the server.
samplesNoDefault 1.
competitorsNoCompetitor names to compare against.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered; the description adds genuinely new behavior: metered billing ('one check per engine per sample') and a plan-tier restriction. The per-engine-per-sample metering formula is the key non-obvious trait since it means cost scales with the engines and samples parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence with the core purpose front-loaded, followed by the two facts that change agent behavior (no tracker, metered, plan-gated). No filler or redundant restatement of the title.

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 six-parameter, read-only tool with an output schema, the description covers the things the schema cannot: cost model, plan eligibility, and the one-off vs. tracker distinction. Only minor gaps remain, such as what happens on an ineligible plan or which sibling to pick for recurring checks.

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 100% schema description coverage the baseline is 3, but the description adds real meaning by explaining that billing scales as engines × samples, which the schema does not state. It reinforces that only one prompt is accepted, matching the required 'prompt' parameter.

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 resource ('AI citation check for a brand and one prompt') plus an explicit scope boundary ('no tracker'), which separates it from the tracker-based siblings like create_citation_tracker and run_citation_tracker. It stops short of naming the alternative tool, so the differentiation is implicit rather than explicit.

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 a clear selection condition ('one-off', 'no tracker') and a hard prerequisite ('Paid plans only (Starter and up)'), which is exactly the kind of gating an agent needs before calling. It does not explicitly say 'use create_citation_tracker instead if you need recurring runs', so the when-not half is only implied.

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

All SEO Score API toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources