Skip to main content
Glama

fedramp_get_rule

Read-onlyIdempotent

Retrieve a FedRAMP rule or NIST control by ID, returning its text and all document locations for citation.

Instructions

Retrieve a rule (or NIST control) by its ID, with every place it appears.

FedRAMP rule IDs look like 'FRC-CSO-FCP', 'VDR-CSO-CVE', 'KSI-IAM-01'; NIST
control IDs look like 'AC-20' or 'SI-4'. The same rule ID often appears in
several documents (e.g. the provider view and the `reference/` rulesets); all
occurrences are returned so you can cite the right context.

Args:
    params (GetRuleInput):
        - rule_id (str): the rule or control ID (case-insensitive).

Returns:
    str: The rule text plus its locations. Markdown by default. Returns an
    actionable error, with close ID suggestions, if the ID is unknown.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds value by specifying that all occurrences are returned, the format is Markdown, and errors include close ID suggestions. This goes beyond the annotations, though it doesn't discuss other behaviors like rate limits or authentication.

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 brief but information-dense: a one-sentence purpose, followed by examples of ID formats, and clear return/error behavior. It is well-structured and front-loaded, with no wasted words.

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 tool's simplicity (one parameter), complete annotations, and the presence of an output schema, the description covers all essential aspects: what the tool does, ID formats, return content, and error handling. It is fully sufficient for an agent to use correctly.

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?

The input schema provides a description for rule_id (including case-insensitivity and examples), and the tool description repeats similar info. With 100% schema coverage (the schema description is non-empty), the description adds marginal value beyond the schema, warranting a baseline of 3.

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 specifies 'Retrieve a rule (or NIST control) by its ID, with every place it appears.' It contrasts with sibling tools (e.g., fedramp_search) by focusing on retrieval by known ID and returning all occurrences, making its purpose distinct.

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: when you have a known FedRAMP or NIST control ID and need all occurrences across documents. Examples of IDs are given, but it doesn't explicitly state when not to use (e.g., for searching unknown IDs) or mention alternatives like fedramp_search.

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/dan-fedramp/fedramp-rules-mcp'

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