Skip to main content
Glama
Trestle MCP

Trestle MCP

Official

Convert FedRAMP XLSX to OSCAL POA&M

trestle_task_xlsx_to_oscal_poam
Destructive

Convert a FedRAMP XLSX POA&M spreadsheet into an OSCAL plan-of-action-and-milestones JSON file, auto-generating linked observations and risks for each POA&M item.

Instructions

Convert a FedRAMP XLSX spreadsheet to an OSCAL POA&M JSON file.

This tool runs the trestle task xlsx-to-oscal-poam command, which reads a FedRAMP-format .xlsx spreadsheet and produces an OSCAL plan-of-action-and-milestones .json file. The converter auto-generates the observations[] and risks[] and cross-links each poam-item to them with deterministic UUIDs.

This command must run inside a trestle workspace: initialize one first with trestle_init and pass its path as trestle_root (or run from within it).

The spreadsheet must have:

  • Row 1: title

  • Rows 2-4: instructions (ignored)

  • Row 5: column headers

  • Row 6+: data rows

Required columns:

  • POAM ID, Weakness Name, Weakness Description, Controls

Args: params (TrestleTaskXlsxToOscalPoamInput): Input parameters with: - title (str): POA&M title (required) - version (str): POA&M version (required) - xlsx_file (str): Path to the input .xlsx file (required) - output_dir (str): Output directory for the OSCAL JSON (required) - work_sheet_name (Optional[str]): Worksheet name (default: 'Open POA&M Items') - system_id (Optional[str]): System identifier (optional) - output_overwrite (bool): Overwrite existing output (default: true) - validate_required_fields (str): Required-field check: on/warn/off (default: warn) - quiet (bool): Suppress per-item output (default: false) - trestle_root (Optional[str]): Trestle workspace root path (optional) - verbose (bool): Display verbose output (optional)

Returns: str: Success or error message with output file location

Examples: - Use when: "Convert this FedRAMP POA&M spreadsheet to OSCAL" - Use when: "Generate plan-of-action-and-milestones.json from an xlsx" - Don't use when: The input is a CSV, or is missing required columns

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "params": "<params>"
    },
    "name": "trestle_task_xlsx_to_oscal_poam"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false; the description reinforces this by stating output_overwrite defaults to true and that existing output is replaced, and it discloses deterministic UUID generation and the generated observations[]/risks[] structure. It does not say what happens when required columns are missing beyond the validate_required_fields default, which is a minor residual gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and prerequisites are front-loaded, which is good, but the Args block largely duplicates parameter descriptions already present in the nested schema. The spreadsheet layout is stated twice (in the prose and again in the xlsx_file schema description), adding length without new 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?

Covers everything an agent needs to invoke this destructive file-producing task correctly: workspace prerequisite, exact spreadsheet row semantics, required columns, output location, and overwrite behavior. With an output schema present and a return-value note supplied, nothing material is missing.

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 description coverage is reported as 0%, so the description must carry the load; it enumerates every parameter with type, required status, and defaults (work_sheet_name, validate_required_fields on/warn/off, trestle_root, quiet, verbose). It adds the spreadsheet row/column contract, which is the key semantic an agent needs, though it mostly restates the nested schema descriptions.

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?

States a specific verb and both resources (FedRAMP XLSX -> OSCAL POA&M JSON) and names the underlying command. Siblings produce OSCAL catalogs/components or handle CSV-to-OSCAL conversions, so the resource produced here clearly distinguishes it.

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?

Provides explicit 'Use when' and 'Don't use when' examples plus a hard prerequisite (must run inside a trestle workspace, initialize first with trestle_init). The exclusion for CSV input is stated but does not point to the sibling that would handle CSVs, so an agent must still infer the redirect.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.