Skip to main content
Glama
Sign In
mendrift-mcp

mendrift-mcp

by suneel190700
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

propose_rollback

Generate a rollback plan for a model to review before execution. Provide the model name, current version, and reason to receive a step-by-step plan for human approval.

Instructions

Generate a rollback plan for human review. Read-only — does not execute.

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": {
      "model_name": "<model_name>",
      "current_version": "<current_version>",
      "reason": "<reason>"
    },
    "name": "propose_rollback"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYes
model_nameYes
current_versionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states 'Read-only — does not execute,' which is a critical safety trait. However, it does not mention what the generated plan contains, whether any state changes occur, or any permission requirements.

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 extremely concise and front-loaded: 'Generate a rollback plan for human review' states the core purpose immediately, followed by the key safety qualifier. Every word earns its place, and there is no filler.

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?

Given the moderate complexity of 3 required parameters and no parameter descriptions, the description is too minimal to enable correct invocation. It explains the main purpose and safety, but the lack of parameter semantics and any contextual guidance about when to generate a rollback plan leaves significant gaps.

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

Parameters1/5

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

The input schema has 3 required parameters with zero description coverage, and the tool description does not explain what model_name, current_version, or reason should contain or how they are used. The description completely fails to compensate for the lack of schema-level parameter documentation.

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: 'Generate a rollback plan for human review.' It clearly distinguishes the tool from siblings like execute_rollback by adding 'Read-only — does not execute,' making the purpose unambiguous.

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 provides clear context: it is for generating a plan for human review, not for executing it. The 'does not execute' phrase implicitly tells the agent not to use this tool when an actual rollback is needed, but it does not explicitly name alternatives or give more detailed when-to-use guidance.

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