Skip to main content
Glama

mind_plan

Read-onlyIdempotent

Classify changed files to determine required gates and isolation needs, or order a file-specific work plan. Returns planning guidance only and never runs checks.

Instructions

Classify changed files and return Mind's planned gates and isolation needs. Use steps for an ordered file-specific work plan; neither runs checks.

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

Input Schema

NameRequiredDescriptionDefault
filesNoFile paths to process

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.62.0
    • changedInput schema / properties / files / description
      Previous value: -"files to process"New value: +"File paths to process"
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already establish that this is a safe, read-only, idempotent, non-destructive, closed-world operation. The description adds meaningful behavioral context beyond annotations: it classifies changed files, returns planned gates and isolation needs, and explicitly states that checks are not run. It does not describe output shape, but the behavioral scope is well covered.

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 two sentences and front-loads the primary action before giving routing and boundary information. Every sentence carries useful information: the first states what is returned, and the second distinguishes from steps and clarifies that checks are not executed. There is no redundant or filler text.

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

Completeness4/5

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

For a simple, read-only planning tool with one fully described optional parameter and no output schema, the description provides enough context to call it correctly. It explains what the tool returns at a high level and what it does not do. It could be slightly stronger by indicating behavior when 'files' is omitted or by giving more detail on the returned plan structure, but the essential context is present.

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?

The schema fully describes the single 'files' parameter as file paths to process, so baseline parameter semantics would be adequate at 3. The description adds useful meaning by specifying that these are changed files, not arbitrary files, which helps the agent decide what to pass. No further syntax or format detail is needed for this simple array parameter.

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 and resource: it classifies changed files and returns Mind's planned gates and isolation needs. It also distinguishes itself from the sibling tool 'steps' by saying steps should be used for an ordered file-specific work plan. An agent can understand the tool's role without opening the schema.

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?

The description gives clear routing guidance by directing agents to use 'steps' when they need an ordered file-specific work plan. It also clarifies that neither this tool nor steps runs checks, which implies this is a planning/classification operation rather than execution. It does not explicitly cover every possible alternative, but the named alternative and the execution boundary are sufficient.

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