Skip to main content
Glama
PrefectHQ

prefect-mcp-server

Official
by PrefectHQ

review_rate_limits

Identify rate limit throttling periods and affected operation groups (e.g., runs, deployments) in Prefect Cloud to diagnose HTTP 429 errors.

Instructions

Review rate limit usage for this Prefect Cloud account (Cloud only).

Prefect Cloud API access is governed by rate limits in different categories (runs, deployments, flows, work_pools, writing-logs, etc.). When you see HTTP 429 errors or "Too Many Requests" responses from the Prefect API, use this tool to identify which operation groups were throttled and when.

Queries all common rate limit operation groups and groups consecutive throttled minutes into periods, showing which operation groups were affected during each stretch.

Note: These are not API authentication keys - they're categories of API operations that are rate limited together (e.g., "runs" includes all flow run API calls, "writing-logs" includes log write operations).

Useful for diagnosing why API calls are being rate limited. The response shows:

  • Distinct time periods where throttling occurred

  • Which operation groups were throttled during each period

  • Total denied requests and peak denials per minute for each group

Examples: - Check recent throttling: review_rate_limits() - Custom time range: review_rate_limits(since="2025-09-30T00:00:00Z", until="2025-10-01T00:00:00Z")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sinceNoStart time for usage data (ISO 8601). Defaults to 3 days ago.
untilNoEnd time for usage data (ISO 8601). Defaults to 1 minute ago.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorYes
sinceYes
untilYes
successYes
summaryYes
account_idYes
throttling_periodsYes
Behavior4/5

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

No annotations provided, but the description thoroughly explains what the tool does, including grouping throttled minutes, showing periods and operation groups, and clarifying these are not API keys. It also notes 'Cloud only' constraint.

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 well-structured with a summary, context, usage guidance, output details, and examples. Every sentence is purposeful and concise.

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 simplicity (2 optional params, output schema exists), the description covers when to use, output structure, and constraints. Minor omission: no mention of data retention limits, but overall complete.

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?

Schema coverage is 100% with descriptions for both parameters. The description adds value by providing usage examples that illustrate typical invocations, which helps semantics beyond 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 'Review rate limit usage for this Prefect Cloud account (Cloud only),' specifying a clear verb and resource. No sibling tool covers rate limits, so it distinguishes well.

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 states when to use: 'When you see HTTP 429 errors or "Too Many Requests" responses.' No alternatives are needed as no sibling tools are similar.

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/PrefectHQ/prefect-mcp-server'

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