Skip to main content
Glama
Sign In

SEO Score API

by io.github.SeoScoreAPI
OverviewDiscussionsAdmin

Citation Auto-reload Setting

citation_auto_reload
Read-onlyIdempotent

Read the auto-reload setting for AI citation checks and this month's reloads and charges. Read-only: auto-reload is off unless the account owner turns it on, and it can only be turned on or changed from the dashboard (signed in), never through the API or this server, because turning it on authorizes charges.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive, yet the description still adds real context: the default state is off, only the account owner can enable it, enabling authorizes charges, and the API can never mutate it. That is substantive policy and authorization disclosure beyond the structured hints; only rate-limit or freshness details are absent.

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?

Two front-loaded sentences that lead with what is read and then explain the read-only boundary. Slight redundancy between 'Read-only:' and 'never through the API or this server', but nothing is wasted.

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?

With an output schema present, the description needn't detail return fields, and it nonetheless hints at them. For a zero-parameter read with full annotation coverage, everything an agent needs to call it correctly is present; the only minor gap is not pointing to which sibling handles top-ups or dashboard linking.

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 there is no parameter meaning to add; the schema is trivially complete. Baseline of 4 applies.

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 ('Read the auto-reload setting') and names the returned payload ('this month's reloads and charges'). It does not name a sibling tool by name, but the explicit 'never through the API or this server' line effectively separates it from the mutation/purchase siblings like citation_topup_checkout.

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 context for use (checking the setting and current-month reload activity) and an explicit when-not: any change must be made from the signed-in dashboard, not here. No alternative read tool is named, so it stops short of a full routing statement.

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