Skip to main content
Glama
Sign In
micro-mcp

micro-mcp

by microdotdo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Set Micro record retention

micro_retention_set
Destructive

Set a project-record retention policy from 30 to 3650 days or keep forever. Enable optional automatic pruning while preserving purchases and entitlements.

Instructions

Set keep-forever or a 30–3650 day project-record policy. Automatic pruning is opt-in; purchases and entitlements are never affected.

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": {
      "recordDays": "<recordDays>",
      "confirm": "<confirm>"
    },
    "name": "micro_retention_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoMicro project directory; defaults to the server working directory
confirmYesExplicit confirmation that this retention policy should replace the inspected policy
automaticNo
recordDaysYes

Output Schema

NameRequiredDescriptionDefault
okYes
jsonNo
stderrYes
stdoutYes
commandYes
exitCodeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already flag the tool as destructive and non-read-only. The description adds meaningful context by clarifying that automatic pruning is opt-in and that purchases and entitlements are never affected, which tempers the destructiveness and defines scope. No contradiction with annotations.

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 concise sentences with no filler. The core action is front-loaded, and the second sentence delivers critical caveats about pruning and unaffected data.

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

Completeness3/5

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

The description covers the main behavior and important exclusions, but the missing keep-forever encoding and the range mismatch with the schema prevent an agent from confidently constructing valid parameters. The presence of an output schema covers return-value expectations.

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 description gives some meaning to recordDays ('keep-forever or a 30–3650 day policy') and automatic ('opt-in'), which are not described in the schema. However, it does not specify how to encode keep-forever, and the 30–3650 range conflicts with the schema's effectively unbounded min/max, leaving ambiguity.

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 uses a specific verb ('Set') and resource ('Micro record retention policy') and clearly states the two policy types: keep-forever or 30-3650 day. It implicitly distinguishes from siblings like micro_retention (viewing) and micro_retention_prune (pruning), but does not explicitly name them.

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?

There is no explicit guidance on when to use this tool versus micro_retention or micro_retention_prune, and no mention of inspecting before setting. The note that automatic pruning is opt-in is a usage nuance, but selection criteria and exclusions are missing.

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