micro-mcp

by microdotdo

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Remove Micro spending cap

micro_spending_cap_delete

DestructiveIdempotent

Remove the authenticated account's spending cap after inspecting current usage and policy. Confirm to proceed.

Instructions

Remove the authenticated account spending cap after inspecting current usage and policy.

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

Input Schema

Name	Required	Description	Default
`confirm`	Yes	Explicit confirmation to remove the account spending cap

Output Schema

Name	Required	Description	Default
`ok`	Yes
`json`	No
`stderr`	Yes
`stdout`	Yes
`command`	Yes
`exitCode`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Aug 30, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the description does not need to restate mutation or destructiveness. It adds minor behavioral context ('after inspecting current usage and policy') but does not elaborate on consequences or what happens if the cap does not exist. This is acceptable given the annotations, but not rich.

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?

A single, front-loaded sentence that states the action, the target resource, and the recommended precondition. No wasted words and every element earns its place.

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 one-parameter tool with comprehensive annotations and an output schema, the description is nearly complete. It includes a useful precondition ('after inspecting current usage and policy') and the confirmation requirement is in the schema. It could clarify whether the operation is reversible, but annotations already signal destructive 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?

The input schema covers 100% of parameter documentation, with the description for 'confirm' fully explaining its purpose. The tool description adds no information about the parameter beyond what the schema already provides, so a baseline 3 is appropriate.

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 states a specific action ('Remove') and the resource ('authenticated account spending cap'), making it easy to distinguish from its sibling micro_spending_cap_set. The qualifier 'after inspecting current usage and policy' adds context without obscuring the core purpose.

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 implies the appropriate usage context: remove the cap after reviewing current usage and policy. It does not explicitly name alternatives like micro_spending_cap_set, but the purpose is clear enough that an agent would know when to use this tool versus setting a cap. A brief exclusionary note would push this to a 5.

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

Deploy Server