Skip to main content
Glama

fedramp_search

Read-onlyIdempotent

Search the FedRAMP 2026 rule corpus using BM25 relevance ranking. Returns matching documents with snippets and paths for easy retrieval of full text.

Instructions

Full-text search across the FedRAMP Consolidated Rules for 2026 corpus.

Ranks all bundled markdown documents (rules, definitions, control guidance,
agency/assessor/advisor guidance) by BM25 relevance to the query and returns
the best matches with a snippet and the document path. Use the returned
`path` with `fedramp_get_document` to read the full text, or use
`fedramp_get_rule` / `fedramp_get_definition` for a specific ID or term.

Args:
    params (SearchInput):
        - query (str): keywords or a rule ID to search for.
        - section (Optional[str]): path-prefix filter (e.g. 'providers/20x').
        - limit (int): max results, 1-30 (default 8).
        - response_format (ResponseFormat): 'markdown' (default) or 'json'.

Returns:
    str: Ranked results. JSON schema when response_format='json':
    {
      "query": str,
      "count": int,
      "results": [
        {"path": str, "title": str, "section": str,
         "score": float, "snippet": str}
      ]
    }
    Markdown otherwise. Returns a "No matches" message if nothing is found.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already declare read-only and idempotent behavior. The description adds details about BM25 ranking, output format, snippet generation, and the 'No matches' response, all consistent with annotations.

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?

Well-structured with front-loaded purpose and usage, but slightly verbose with detailed args/returns. Could be trimmed slightly without losing clarity.

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?

Comprehensively covers the search behavior, ranking, filtering, output formats, error handling, and links to sibling tools. Complete for a search tool with two output modes and multiple parameters.

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?

Though the schema has basic descriptions, the overall param description coverage is 0% for the top-level 'params' parameter. The description compensates by explaining each parameter's purpose, accepted formats (e.g., 'keywords or a rule ID'), and defaults.

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?

Clearly states the tool performs full-text search across the FedRAMP rules corpus, specifies the verb and resource, and distinguishes from siblings by mentioning follow-up tools like fedramp_get_document.

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 tells when to use this tool (initial search) and when to use alternatives (fedramp_get_rule, fedramp_get_document) for retrieving specific items, providing clear guidance on the workflow.

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