Skip to main content
Glama
MSPbotsAI

openai-workspace-mcp

by MSPbotsAI

openai_update_rate_limit

Update rate limits for a model in an OpenAI project, setting per-minute or per-day caps for requests, tokens, images, audio, and batch input.

Instructions

Update a project's rate limit for one model.

    Each `max_*` field only applies to relevant model types (e.g.
    max_images_per_1_minute only matters for image models) — check
    openai_list_rate_limits first to see which fields are present for the
    target model before changing them.

    Args:
        project_id: The project's ID (see openai_list_projects).
        rate_limit_id: The rate limit entry's ID (see openai_list_rate_limits).
        max_requests_per_1_minute: New requests-per-minute limit.
        max_tokens_per_1_minute: New tokens-per-minute limit.
        max_images_per_1_minute: New images-per-minute limit.
        max_audio_megabytes_per_1_minute: New audio-megabytes-per-minute limit.
        max_requests_per_1_day: New requests-per-day limit.
        batch_1_day_max_input_tokens: New batch max input tokens per day.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
rate_limit_idYes
max_requests_per_1_dayNo
max_images_per_1_minuteNo
max_tokens_per_1_minuteNo
max_requests_per_1_minuteNo
batch_1_day_max_input_tokensNo
max_audio_megabytes_per_1_minuteNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations provided, the description must disclose behavior. It warns that each 'max_*' field only applies to relevant model types, which is a valuable non-obvious constraint. But it does not clarify whether omitted fields are left unchanged or reset to null, nor the effect of passing null values.

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?

The description is front-loaded with the purpose, includes a focused caveat about model types, and uses an Args block for parameter details. It is slightly verbose with repetitive 'New ...' phrasing, but every sentence contributes useful information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 8 parameters and an output schema; the description covers the main caveat and references sibling tools for ID lookup. However, it omits whether updating with no optional parameters is a valid no-op and does not specify that the update is partial (only provided fields change), leaving a gap for a mutation tool.

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 description lists all 8 parameters and adds explanatory context, such as 'New requests-per-minute limit' and references for project_id and rate_limit_id. Since schema description coverage is 0%, this compensation is valuable, though some entries simply restate the parameter names without deeper detail.

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 'Update a project's rate limit for one model' with a specific verb and resource. It distinguishes the tool from sibling openai_list_rate_limits, which is a read-only listing operation.

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 explicitly instructs to 'check openai_list_rate_limits first' to see which fields are present, providing a clear prerequisite for correct usage. However, it does not explicitly state when not to use this tool or contrast it with other update tools.

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/MSPbotsAI/openai-workspace-mcp-'

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