Skip to main content
Glama

Black SEO Analyzer

account_status

Read-onlyIdempotent

Report this account's plan and usage live: whether hosted audits are active, the page budget used and remaining in the rolling 30 days and when it resets, how long crawl sessions are kept, and the licenses on the account. Call it when a tool returned trial_expired, no_hosted_addon or quota_exceeded, when the user says their plan has changed, or when they ask what their plan includes. Read-only: it never changes the account.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the closing 'Read-only: it never changes the account' largely restates them. What the description does add beyond annotations is behavioral value: it declares the data is live (not cached), specifies the rolling 30-day quota window with a reset point, and pins down crawl-session retention — facts an agent needs to interpret the response. A minor deduction for the redundant safety sentence.

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 sentences, front-loaded with the payload content, followed by trigger conditions. Efficient overall, though the trailing 'Read-only: it never changes the account' duplicates the readOnlyHint annotation and could be dropped without loss.

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?

With no output schema present, the description carries the burden of describing return values — and it does so field by field (hosted audit activity, page budget used/remaining and reset, retention period, licenses). For a zero-parameter read tool this is complete enough to call correctly and to interpret results.

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 nothing for the description to disambiguate; the baseline for a 0-param tool applies. No param-level meaning is missing because no inputs exist.

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?

The description opens with a specific verb and resource — 'Report this account's plan and usage live' — then enumerates the exact contents (hosted audit status, page budget used/remaining over a rolling 30 days and reset timing, crawl-session retention, licenses). No sibling tool (crawl_status, list_crawls, query_issues) covers account-level plan/usage, so the boundary is unambiguous.

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 names concrete triggers: when a tool returned trial_expired, no_hosted_addon or quota_exceeded, when the user says their plan changed, or when they ask what the plan includes. That is explicit when-to-use guidance tied to observable signals, leaving little to inference.

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.