Skip to main content
Glama

List limit requests

list_limit_requests
Read-only

The organisation's latest limit-increase request per kind (the twin of ankra org limits list): what was requested, the justification, and whether it is pending, approved or rejected. Requires billing.read. Read-only; request_limit_increase files a new one.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces that while adding genuinely new context: the required billing.read permission scope and a description of what is returned (one latest entry per kind, with status states). It stops short of noting ordering, volume, or edge cases like no requests existing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence carries scope, returned content, the permission requirement, and the sibling distinction with no filler. The parenthetical CLI alias is mildly extraneous but serves as an identity anchor for agents familiar with the CLI.

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?

With no input parameters and no output schema, the description must carry the return shape, which it does by naming the fields and status values. A note on ordering or behavior when no requests exist would close the last gap.

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 semantics to explain and the baseline of 4 applies. Nothing in the description misleads about inputs.

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?

States a specific verb and resource with scope ('latest limit-increase request per kind') and enumerates the returned fields (what was requested, justification, status). It also names its mutating sibling, so an agent can separate it from request_limit_increase without opening either schema.

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?

Explicitly frames itself as the read path and points at request_limit_increase as the tool that files a new request, plus states the 'read-only' constraint. It does not spell out an explicit 'do not use this to create requests' exclusion, but the contrast is clear enough.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.