Skip to main content
Glama

create_rate_limit

Create a rate limit to throttle requests or tokens by time unit, with conditions and grouping for precise control.

Instructions

Create a request or token throttle with conditions, group_by, type, unit, and value. conditions and group_by are required; use usage limits when you need a cumulative budget instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
conditionsYesArray of conditions that determine which requests this rate limit applies to
group_byYesArray of fields to group the rate limit by (e.g., ['virtual_key'], ['api_key', 'user_id'])
typeYesWhat to rate limit: 'requests' or 'tokens'
unitYesTime unit: 'rpm' (per minute), 'rph' (per hour), or 'rpd' (per day)
valueYesThe maximum allowed value per unit (e.g., 100 rpm)
nameNoOptional name for the rate limit
workspace_idNoWorkspace ID to scope the limit to
organisation_idNoOrganisation ID to scope the limit to

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool call succeeded and returned structured data
dataNoStructured success payload when ok is true
errorNoStructured error payload when ok is false
Behavior3/5

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

Annotations provide basic behavioral cues (readOnlyHint false, destructiveHint false, idempotentHint false, openWorldHint true). The description adds no further behavioral context beyond what is already in annotations, but does not contradict them.

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?

The description is a single sentence with an additional sentence for alternative guidance. It is concise, front-loaded, and contains no redundant information.

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?

Given the tool's complexity (8 parameters, 5 required) and the presence of an output schema, the description is mostly complete. It could mention the possibility of duplicate creation, but the annotations and sibling tools provide sufficient context.

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?

Input schema has 100% description coverage for all 8 parameters, so the description adds no additional meaning beyond listing some parameter names and noting that conditions and group_by are required, which is already in the schema.

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 the tool creates a request or token throttle, listing key parameters. It distinguishes itself from the sibling tool create_usage_limit, which is used for cumulative budgets.

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

Usage Guidelines5/5

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

Explicitly states when to use this tool (for rate limiting) and when not (use usage limits for cumulative budgets). Also notes that conditions and group_by are required.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/s-b-e-n-s-o-n/portkey-admin-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server