Skip to main content
Glama

Get spending and rate limits

autoshort_get_limits
Read-onlyIdempotent

Check credit balance, daily spending cap, auto-recharge status, publishing limits, and hourly free AI caps to identify what may block an AutoShort call.

Instructions

Everything that can stop a call: credit balance, this key's daily agent spending cap (spent / remaining / reset), auto-recharge status and monthly cap, platform publishing limits, and per-hour caps on free AI calls. 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_get_limits"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that by disclosing that the call is free and by enumerating exactly which limit categories are reported, including the reset window on the daily cap. It does not describe the response shape, but with zero parameters and a read-only profile the remaining burden is small.

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 sentence with the highest-value concept ('everything that can stop a call') front-loaded, followed by a compact enumeration and a one-word cost note. No filler, no restatement of the title, nothing to cut.

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?

There is no output schema, so the description carries the return-value burden, and it does so by listing the reported fields with enough granularity (spent/remaining/reset, monthly cap, per-hour caps) for an agent to know what it will get back. It does not state the response format or units, which is a minor residual gap for a zero-parameter read.

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 no parameters, so there is no parameter meaning to add; baseline 4 applies. The description correctly implies a parameterless, context-free call by not mentioning any inputs.

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 names a concrete resource set with unusual specificity: credit balance, per-key daily spending cap with spent/remaining/reset, auto-recharge status and monthly cap, publishing limits, and hourly free-AI-call caps. That enumeration clearly separates it from narrow siblings like autoshort_get_credit_balance and from the mutating autoshort_set_limits. It stops short of a clean verb-first framing, opening instead with the phrase 'Everything that can stop a call'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the framing 'Everything that can stop a call' suggests a pre-flight check before invoking generating tools, and 'Free.' signals it costs nothing to call. There is no explicit when-to-use statement, no mention of the alternative narrower tools (credit balance, usage stats, subscription), and no exclusions.

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