Skip to main content
Glama

mind_classify

Read-onlyIdempotent

Classifies a set of changed files by category and risk to show what proof a change owes before landing; does not run verification.

Instructions

Classify a set of changed files by category and risk. Use proof for a single file's planned gates; this does not run verification.

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

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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: the tool analyzes rather than verifies, which prevents an agent from assuming a passing classification means a passing gate. It does not describe the category set, risk levels, or failure behavior for unparseable paths.

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?

Two short sentences, zero filler, with the core action front-loaded and the alternative and boundary trailing as qualifications. Every clause carries information.

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, optional-parameter, read-only analysis tool with no output schema, this covers what it does, what it does not do, and when to pick a sibling. The one remaining gap is that the meaning of the returned categories and risk values is left unspecified.

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

Parameters3/5

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

With a single parameter at 100% schema coverage, the schema already documents 'files' as file paths; the baseline is 3. The description only adds that these should be changed files, implying diff-derived input, and says nothing about how relative paths or non-existent files are handled.

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 names a specific verb (classify) and resource (a set of changed files) and adds the two output dimensions, category and risk. It also names the sibling it is not, 'proof', so an agent can separate the two without opening a 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?

It gives an explicit routing rule for the closest alternative: use 'proof' when the task is a single file's planned gates. It also states a negative boundary ('this does not run verification'), but it offers no guidance for the other siblings (mind_plan, mind_route, gate) or for edge cases such as empty or non-code file lists.

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