Skip to main content
Glama

AINDEX

A first plan for an agent, from one sentence

plan_agent
Read-only

Turn one sentence about what an agent should do ("Earn funding on NVDA without betting on its price", "Lend my idle USDG on Morpho", with an amount if you like) into the same first plan the AINDEX front page shows: what it would hold and where, how it decides, how free it is, its daily loss limit, and what it can never do. Plus the link that starts it on the website. A keyword sketch, not the agent: the agent writes its real plan once started.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "plan_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesWhat the agent should do, in the person's own words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds valuable context beyond that: it lists what the response contains (holdings, decision logic, freedom, daily loss limit, never-do constraints), mentions the included website link, and warns that the output is a keyword sketch rather than the real plan.

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?

The description is front-loaded with the core action and follows with a compact list of what the plan includes and the caveat that it is a sketch. It is somewhat dense, especially the parenthetical examples, but every sentence contributes useful context and there is no filler.

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?

There is no output schema, so the description carries the burden of explaining what comes back, and it does so by enumerating the plan elements and the website link. For a one-parameter, read-only planning tool, it supplies enough context about input, output, and next steps that an agent can call it correctly.

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?

Schema coverage is 100%, so the schema already documents the single 'text' parameter as the person's own words. The description adds meaning with concrete input examples ('Earn funding on NVDA without betting on its price', 'Lend my idle USDG on Morpho') and notes that an amount is optional, which goes beyond 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 uses a specific verb ('Turn one sentence ... into') and names the exact artifact produced: 'the same first plan the AINDEX front page shows.' It further distinguishes the tool from actual agent creation by stating it is 'A keyword sketch, not the agent,' so an agent can tell it apart from create_agent without opening schemas.

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 gives clear context for when to use it: to preview the first plan from a one-sentence description, with a link to start the agent on the website. It also implicitly excludes using it as the creation step ('not the agent: the agent writes its real plan once started'), though it does not explicitly name create_agent as the alternative.

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