serpmantics

get_aissistant_tokens

get_aissistant_tokens

Get the current user's available AI tokens

Returns the number of AI tokens available to the authenticated user.

These tokens fund EVERY AI feature in SERPmantics — meta, outline, intent, internal-links, EEAT, EEAT competitors, score, AND the AISSistant prompts. The endpoint lives under /aissistant for historical reasons but the balance is shared across all AI features.

Do NOT confuse with guide-creation credits (see /api/v1/credits). For a combined view (credits + tokens) prefer /api/v1/credits.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A5/5.0

Behavior5/5

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

No annotations provided, but description fully discloses behavior: tokens fund all AI features, lists them, clarifies historical endpoint naming, and implies read-only access. No destructive behavior mentioned.

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?

Six sentences, each adding value: core purpose, scope details, shared nature, historical context, warning about confusion, and alternative endpoint. No waste.

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?

Given no parameters, no output schema, and no annotations, the description is sufficient for agent selection and invocation. Explains token usage, related endpoints, and potential confusion with credits.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has no parameters (0 params, baseline 4). Description adds meaning by explaining what tokens are used for across features, providing context beyond schema.

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 clearly states it 'Get the current user's available AI tokens' with a specific verb and resource. It distinguishes from sibling tools by noting it is not for guide-creation credits and directing to a combined view.

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?

Provides explicit guidance: 'Do NOT confuse with guide-creation credits (see /api/v1/credits). For a combined view (credits + tokens) prefer /api/v1/credits.' Also explains the historical naming reason.

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

All serpmantics tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0

Disambiguation4/5

Most tools target distinct resources (guides, eeat, intent, internal_links, meta, outline, score, credits, tokens). However, some pairs like create_eeat and create_eeat_competitors are very similar and could cause confusion, though their descriptions clarify the difference.

Naming Consistency4/5

Tools consistently use a verb_noun pattern (create_, get_, delete_). Minor inconsistencies include 'get_aissistant_tokens' (typo) and 'get_credit_ledger' (singular vs plural), but overall the pattern is clear.

Tool Count4/5

28 tools is on the higher end but justifiable for a comprehensive SEO analysis platform covering guides, multiple AI features, EEAT, credits, and tokens. A few tools could be merged (e.g., get_credits and get_aissistant_tokens), but the count is still reasonable.

Completeness4/5

The tool surface covers CRUD for guides and most AI features, plus token/credit management. A notable gap is the lack of a get_score tool after create_score, and some features like updating EEAT analysis are absent. Overall, the core workflows are supported.

Resources

Need Help?