Atomadic MCP

Agents Plan

agents_plan

Read-onlyIdempotent

[agents] Autonomous agent goal planning

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": {
      "goal": "<goal>"
    },
    "name": "agents_plan"
  }
}

Input Schema

Name	Required	Description	Default
`goal`	Yes
`constraints`	No	Optional constraints for the plan (e.g., time limits, resource caps)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

C2/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, but the description adds no behavioral context beyond the name. It says nothing about plan structure, whether the agent executes the plan, determinism, or what the response contains.

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

Conciseness2/5

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

The single phrase is not concise so much as under-specified. It contains no front-loaded useful detail and omits nearly everything an agent needs to select and invoke the tool correctly.

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

Completeness2/5

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

For a planning tool with a required goal, a nested constraints object, and no output schema, the description should explain what kind of plan is produced and how constraints affect it. Instead it provides only a restatement of the name, which is inadequate for the tool's complexity.

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

Parameters2/5

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

Schema coverage is only 50% and the description provides no meaning for either parameter. The required 'goal' parameter has only an example in the schema, and the nested 'constraints' object receives no explanation in the description, so the description fails to compensate for the coverage gap.

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

Purpose2/5

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

The description 'Autonomous agent goal planning' essentially restates the tool name and title without a concrete verb or stated outcome. It does not clarify whether the tool generates a plan, registers a goal, or executes steps, leaving it ambiguous among the many agents_* siblings.

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?

There is no guidance on when to use this tool, when not to, or which sibling alternatives exist. The agent must infer usage from the name alone.

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

All Atomadic MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?