Skip to main content
Glama

get_limits

Read-onlyIdempotent

Read account-wide plan limits for concurrency, batch size, and pending jobs, plus the current pending-job count, to verify shared quotas across all API keys.

Instructions

Read account-wide plan concurrency, batch size and pending-job limits, plus current pending-job count. Limits are shared by all keys, not remaining concurrency slots. 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": "get_limits"
  }
}

Input Schema

NameRequiredDescriptionDefault
response_formatNoAgent-readable presentation. MCP defaults to Markdown; json returns the original JSON text, text returns indented fields. Structured fields remain available. Does not change billing or the stored job.markdown

Output Schema

NameRequiredDescriptionDefault
codeNoMachine-readable error code when the operation fails.
noteNoLimit snapshot limitations.
planNoCurrent account plan.
scopeNo
detailNoAdditional problem detail returned by the API.
limitsNoAccount plan ceilings, not remaining slots.
currentNoPoint-in-time pending-job count.
messageNoError, delivery, or continuation instructions.
request_idNoFlashData request identifier for support and tracing.
http_statusNoUpstream HTTP status, when an upstream request was made.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description is correctly focused on semantic behavior. It adds genuinely useful context beyond the schema and annotations: these are account-wide ceilings shared across keys, not remaining concurrency, and calls are free (no billing impact). Return shape is covered by the output schema, so its omission is not a gap.

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 tight sentences with zero waste: what is returned first, then the interpretive caveat. The most load-bearing clarification (shared limits vs. live slots) is placed immediately after the payload description.

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 simple, read-only, single-parameter tool with an output schema and rich annotations, the description supplies what the structured fields cannot: that the numbers are plan ceilings shared by all keys and that the call is free. The only missing element is explicit guidance on choosing this over get_balance or get_usage.

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 single response_format parameter is fully documented in the schema (100% coverage, enum values and default explained), so the description need not repeat it. The description adds no parameter meaning beyond the schema, which is acceptable at this coverage level — the baseline 3 applies.

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?

States a specific verb and resource set: reads account-wide plan concurrency, batch size, and pending-job limits plus the current pending-job count. Scope is unambiguous (account-wide) and distinguished from live state via 'not remaining concurrency slots'. It does not name a sibling such as get_balance or get_usage outright, so cross-tool differentiation is only partial.

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 implied rather than stated: the caveat about limits being shared by all keys and being distinct from remaining concurrency slots implies this is the call for static plan ceilings before or instead of checking live slots. There is no explicit when-to-use/when-not or named alternative, so an agent must infer the routing decision.

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