AnimatedWebs

Get AnimatedWebs pricing

get_pricing

Read-onlyIdempotent

Returns AnimatedWebs plans and prices (Free, Prompt Pack, Pro monthly and yearly, Lifetime) with what each includes, founding Lifetime spots left and the pricing page URL. Use it for plan and price questions; use get_account for the signed-in user's own plan, credits and usage. Prices are numbers in USD; only the founding or the regular Lifetime plan is listed, depending on spots left. No parameters. Read-only. Example: {}.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`free`	Yes
`plans`	Yes
`includes`	Yes
`pricingUrl`	Yes
`foundingLifetimeSpotsLeft`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 8, 2026
- addedOutput schema / properties / plans / items / properties / price / description
```
Added value: +"USD"
```
First observedNov 2, 2026

TDQS

A4.7/5.0

Behavior4/5

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

The annotations already declare this operation read-only, idempotent, non-destructive, and closed-world. The description adds useful behavioral detail beyond that: prices are in USD, only the founding or regular Lifetime plan is listed depending on available spots, and there are no 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?

The description is front-loaded with the return contents, then gives the routing guidance, then notes pricing caveats. It is dense but every clause carries useful information.

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 an output schema present, the description does not need to restate the return shape. It covers purpose, scope, alternative tooling, pricing quirks, and the zero-parameter calling convention.

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?

This tool takes zero parameters, so there is no parameter semantics to explain. The description still explicitly states 'No parameters' and gives an empty-object example, which matches the 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 gives a specific verb and resource: it returns AnimatedWebs plans and prices, and lists the exact plan tiers covered. It also distinguishes this from get_account, which handles the signed-in user's own plan, credits, and usage.

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 explicitly says to use this tool for plan and price questions and names get_account as the alternative for account-specific plan, credits, and usage. The selection condition between the two tools is clear.

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

All AnimatedWebs tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.