Skip to main content
Glama

The plan

plan
Read-only

The ranked queue for this week, built only from what the latest access audit unlocked: { rank, module, title, why, command, price, evidence? }, and the founder's stage: zero (no payment seen yet) puts what wins a first customer first. evidence is what an item rests on: a number of the founder's own (signal), the play library's best grade for that kind of move (grade, library) and what it did for this founder before (past). Free. Work it top down; state the credits before running anything priced over 5.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already mark it read-only and safe. The description adds non-obvious behavior: it is free, depends on the latest access audit, and warns to state credits before running priced items over 5. This adds useful operational context beyond annotations.

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?

The description front-loads the core concept ('ranked queue for this week') but the long first sentence with nested colons and parentheticals is hard to parse. The evidence explanation is useful but could be structured as bullets. Adequate but not efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read tool with no output schema, the description must explain return values. It outlines fields and evidence meanings, but leaves 'module' and 'command' undefined and does not clarify what happens when no access audit exists. Some gaps remain.

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?

Zero parameters, so the schema is empty and description need not explain inputs. Baseline 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

It describes a 'ranked queue for this week' but does not start with a clear verb, uses dense jargon ('latest access audit unlocked', 'founder's stage: zero'), and does not distinguish from siblings like today or offer_plan. The intent is inferable but not crisp.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is 'Work it top down; state the credits before running anything priced over 5,' which concerns consuming results, not when to choose this tool over alternatives. No conditions for use or exclusions are provided.

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.

Resources