Skip to main content
Glama

fedramp_list_documents

Read-onlyIdempotent

Browse the FedRAMP document corpus by listing documents with optional section filters, returning paths and titles for easy navigation.

Instructions

List documents in the corpus, optionally filtered to a section prefix.

Useful for browsing the structure before drilling in. Sections include
'advisors', 'agencies', 'assessors', 'authority', 'providers', 'reference',
'responsibilities', plus top-level files (definitions.md, rules.md, ...).

Args:
    params (ListDocumentsInput):
        - section (Optional[str]): path-prefix filter (e.g. 'reference/controls').
        - response_format (ResponseFormat): 'markdown' (default) or 'json'.

Returns:
    str: List of {path, title}. JSON schema when response_format='json':
    {"section": str|null, "count": int,
     "documents": [{"path": str, "title": str}]}

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 indicate read-only and idempotent behavior. Description adds context on optional filtering and return format, which goes beyond what annotations provide.

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 a summary sentence, usage context, section list, and clear Args/Returns sections. Slightly verbose with the section list but overall efficient.

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?

Covers input parameters and output format thoroughly. Lacks mention of pagination or limits, but for a browsing tool this is acceptable.

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

Parameters5/5

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

Description explicitly explains both parameters (section and response_format) with types and defaults, compensating for the 0% schema description 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?

Clearly states verb 'List' and resource 'documents in the corpus', with optional filtering by section. Distinguishes from sibling tools that get specific documents or search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a hint on when to use ('browsing the structure before drilling in') and lists sections, but does not explicitly state when not to use or compare to alternatives.

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