Skip to main content
Glama

cf_get_managed_rule_details

Retrieves the full definition of a managed ruleset rule by its ID, enabling false-positive triage by revealing what the rule matches.

Instructions

Look up details of a specific managed-ruleset rule (account-scoped).

Managed rulesets are owned by Cloudflare and live at the account scope;
individual managed rules are referenced from a zone's deployment.
This tool is the bridge: given a managed (ruleset_id, rule_id), it
returns the full rule definition so the agent can determine what the
rule actually matches (used for FP triage on managed-rule hits).

Calls: GET /accounts/{account_id}/rulesets/{ruleset_id} → project rule.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYes
ruleset_idYes
rule_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries full behavioral disclosure burden. It describes the operation as a GET call returning the full rule definition, and adds context about scope and relationship to zone deployment. It does not detail side effects, permissions, or error cases, but the behavior is straightforward for a read-only lookup.

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 concise with two short paragraphs, front-loading the purpose. Every sentence adds value, including the API call line. No redundant or irrelevant information.

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

Completeness5/5

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

Given the output schema exists, the description need not explain return values. It provides sufficient context: the tool's role as a bridge, its use for FP triage, and its relationship to zone-level deployment. This is complete for a detail-lookup tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must fully document parameters. The description mentions 'ruleset_id' and 'rule_id' but omits 'account_id' explicitly, though implied by 'account-scoped'. It lacks individual parameter explanations, which is insufficient given the 0% coverage.

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 'Look up details of a specific managed-ruleset rule' with a specific verb and resource. It distinguishes from sibling tools by noting the account scope and its role as a bridge for FP triage, making the purpose unambiguous.

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?

The description explains when to use the tool (for FP triage on managed-rule hits) and mentions the API endpoint. It does not explicitly list alternatives or when not to use, but the context is clear given sibling tool names.

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/wojtekkura/cf-mcp'

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