Skip to main content
Glama
Sign In
AIMFP

AIMFP

by aryanduntley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

reorder_completion_path

Reorder a completion path by updating its order index to change its position in the task sequence.

Instructions

Change order_index for a completion path

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": {
      "id": "<id>",
      "new_order_index": "<new_order_index>"
    },
    "name": "reorder_completion_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCompletion path ID
new_order_indexYesNew order position

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.37.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations indicate a write operation (readOnlyHint=false) but not destructive. The description adds no behavioral context beyond what annotations provide, such as potential side effects on other completion paths or authorization needs.

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 a single sentence of 5 words, highly concise and to the point. It effectively communicates the core action without unnecessary verbosity.

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?

Despite low complexity (2 parameters, no nested objects), the description lacks important context such as the effect on other paths, return value (no output schema), or error conditions. It is insufficient for an agent to fully understand the tool's behavior.

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?

Both parameters are described in the schema with clear names ('id' and 'new_order_index') and descriptions ('Completion path ID', 'New order position'). The description adds no additional semantic value beyond the schema, achieving baseline score given 100% coverage.

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

Purpose4/5

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

The description 'Change order_index for a completion path' clearly identifies the verb 'change' and the resource 'order_index' for a 'completion path'. While specific, it does not distinguish itself from sibling tools like 'reorder_all_completion_paths' or 'swap_completion_paths_order'.

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 description provides no guidance on when to use this tool, prerequisites, or alternatives. No context signals are given to help an agent decide between this and related tools.

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

Deploy Server

Other Tools