past.dev

Show the plan

get_plan

Read-onlyIdempotent

The organization's plan: the credits it includes and whether they come back each billing period or were granted once, how many content bytes buy a credit, what one recall costs, the fair use on recall where the plan has one (this billing period's figure, the recalls served against it, and what a recall above it costs), any cap on recalls, how long request payloads are kept, how long unused credits roll over, and what happens when the credits run out. Mirrors the plan the Usage screen and the sidebar meter show; every role holds it.

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_plan"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 6, 2026

TDQS

A4.5/5.0

Behavior5/5

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

This description provides extensive behavioral context beyond standard annotations, detailing lifecycle events like how long request payloads are kept and the conditions under which credits run out. This is high-value, functional transparency.

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

Conciseness3/5

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

While comprehensive, the description is overly dense and verbose. It functions more like a knowledge dump than a concise instruction, which slightly hinders agent readability despite its thoroughness.

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 the complexity of the plan (involving multiple types of charges and temporal rules) and the absence of an output schema, this description is exceptionally complete, covering nearly every operational detail an agent would need to anticipate the response data.

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?

Since there are zero parameters, the description's job is entirely contextual. It adds high value by defining the complex internal data structure and policy that the zero-parameter call will retrieve.

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 moves beyond a simple 'show' operation by specifically detailing the policy aspects of the plan (e.g., rollover, recall costs, byte pricing). This distinguishes it clearly from tools like get_credit_balance or admin_get_contract, focusing instead on the structural definition of the plan.

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?

It provides clear usage context by stating that the information is the same across all UI representations and is accessible to 'every role.' This effectively defines its scope and intended audience without naming explicit alternatives.

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

All past.dev 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.

Resources

Need Help?