Skip to main content
Glama
Sign In
safe-migrations-mcp

safe-migrations-mcp

by possibly6
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cleanup_state

Remove outdated proposal metadata, secret payloads, and snapshots from local state to free up space and maintain a clean environment.

Instructions

Prune old proposal metadata, secret payloads, and snapshots from local state.

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

Input Schema

NameRequiredDescriptionDefault
max_age_daysNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It indicates destructive action ('prune') but lacks details on irreversibility, side effects, or safety considerations. The agent has no indication of data recovery options or whether the operation is safe to run regularly.

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 that efficiently conveys the core action and objects. It is front-loaded and to the point, though it could benefit from slightly more structure (e.g., listing items or parameter clarification).

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 having an output schema, the description omits return value information, side effects, or any process details. Given the lack of annotations and the tool's potentially destructive nature, the description is insufficient for comprehensive understanding.

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?

The schema has 0% description coverage, and the description only vaguely references 'old' data. However, the single optional parameter (max_age_days) is hinted at by the word 'old', and the default value is clear from the schema. The description adds minimal meaning beyond the schema's own structure.

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 clearly identifies the tool's action ('prune') and the specific items (proposal metadata, secret payloads, snapshots) and location (local state), distinguishing it from sibling tools like apply_change or inspect_config.

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?

No guidance is provided on when to use cleanup_state versus alternatives, nor are there any prerequisites or exclusions mentioned. The description simply states what it does without context for selection.

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