Skip to main content
Glama

Turn off auto-recharge

autoshort_disable_auto_recharge
Idempotent

Disable auto-recharge to stop automatic credit purchases immediately. Re-enabling it requires owner approval, giving you control over future charges.

Instructions

Turn auto-recharge off immediately; autoshort_buy_credits stops charging. Turning it back on needs the owner's approval again. Free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, idempotent toggle, so the bar is lower. The description earns credit by adding what the annotations cannot convey: the change is immediate, it halts charging through the named sibling, re-enabling requires owner approval, and the action is free.

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?

Three short sentences, each front-loaded with the most important fact (immediate effect, then consequence for charging, then reversibility and cost). Nothing repeats the name or title and no clause is padding.

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 zero-parameter, non-destructive toggle with annotations covering the safety profile and no output schema, the description covers effect, cost, and reversibility. It could add one line on what state the account is left in (e.g., credits remaining usable) but nothing essential for correct invocation is missing.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly avoids inventing parameters and instead spends its words on effect and consequence.

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 opening clause names a specific verb and resource ('Turn auto-recharge off') and pairs it with an immediate-effect qualifier, so there is no ambiguity about what the call does. It also implicitly contrasts with the setup/enable counterpart by noting that turning it back on requires approval.

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?

It gives clear context for invoking the tool: the effect is immediate, it stops charging via autoshort_buy_credits, and re-enabling requires owner approval. It does not explicitly say when a user should prefer this over alternatives such as checking balance or adjusting limits, so it stops short of full when/when-not guidance.

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