Skip to main content
Glama
Trestle MCP

Trestle MCP

Official

Assemble Profile JSON from Markdown Directory

trestle_author_profile_assemble
Destructive

Assembles an OSCAL profile JSON from a directory of markdown controls and expands parameters to support CI/CD compliance workflows.

Instructions

Assemble markdown controls into a Profile JSON file.

This tool assembles an OSCAL profile JSON (profile.json) from a directory of markdown controls for a profile.

Args: params (TrestleAuthorProfileAssembleInput): - markdown_dir (str): Markdown controls directory (required) - output_profile (str): Output profile directory name (required) - name (Optional[str]): Profile model name - set_parameters (bool): Expand parameters from YAML frontmatter - regenerate (bool): Force UUID regeneration - version (Optional[str]): Model version - sections (Optional[str]): Section info (short:long, comma-separated) - required_sections (Optional[str]): Required section short names, comma-separated - allowed_sections (Optional[str]): Allowed section short names, comma-separated - verbose (bool): Verbose output - trestle_root (Optional[str]): Path of trestle root directory

Returns: str: Success message with stdout, or error message with stderr details

Examples: - Use when: Automatically assemble OSCAL profile from markdown directory - Use when: CI/CD profile assembling, parameter expansion - Don't use when: Input markdown_dir does not exist, or malformed markdown

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_author_profile_assemble"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true and idempotentHint=false, so the safety profile is known. The description adds that it writes a profile.json into an output directory and that 'regenerate' forces UUID regeneration, but it never states whether an existing profile.json is overwritten, nor how the non-idempotent UUID behavior affects repeated runs — the most important behavioral facts for a destructive tool.

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?

The one-line purpose is front-loaded, followed by clearly labelled Args/Returns/Examples sections with no prose padding. Some redundancy exists (the arg list mirrors the schema, the trailing 'Returns: str' duplicates the output schema), but the structure is easy to scan.

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

Completeness3/5

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

An output schema exists, so return-value explanation is not strictly needed, and parameter meanings are covered. What is missing for a destructive, open-world filesystem-writing tool is any statement about overwrite behavior, required directory/permission preconditions, or what happens to an existing output profile — information the annotations flag as critical but the description leaves silent.

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?

Schema coverage is reported at 0%, so the description carries the burden — and it does enumerate all eleven sub-parameters and adds meaning beyond the schema for several (e.g. 'set_parameters: Expand parameters from YAML frontmatter', 'regenerate: Force UUID regeneration'). But most entries merely restate the schema titles without format or example detail, so it only partially compensates for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb+resource: assemble an OSCAL profile JSON (profile.json) from a directory of markdown controls. That is clearly distinguishable from a read/validate tool, but it never contrasts itself with the nearest siblings (trestle_author_profile_generate / profile_resolve), so the agent must infer directionality.

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 Examples block gives two positive 'Use when' contexts (automatic assembly, CI/CD with parameter expansion) and one 'Don't use when' condition. However, the negative case is a precondition ('markdown_dir does not exist, or malformed markdown') rather than a genuine alternative tool, and no sibling is named as the fallback.

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