Skip to main content
Glama
Trestle MCP

Trestle MCP

Official

Resolve Profile to Catalog

trestle_author_profile_resolve
Destructive

Resolve an OSCAL profile into a parameter-resolved profile catalog, with options to control parameter values, labels, and formatting for compliance documentation.

Instructions

Resolve an OSCAL profile to a resolved profile catalog.

This tool resolves a specified OSCAL profile (by name from profiles//profile.json) into an operational, parameter-resolved OSCAL catalog, with flexible output and formatting options.

Args: params (TrestleAuthorProfileResolveInput): - name (str): Source profile name (required) - output (str): Output catalog name (required) - show_values (bool): Show parameter values in prose (optional) - show_labels (bool): Show parameter labels in prose (optional) - bracket_format (str): Bracket format for values (optional) - value_assigned_prefix (str): Prefix if value is assigned (optional) - value_not_assigned_prefix (str): Prefix if value not assigned (optional) - label_prefix (str): Prefix for label output (optional) - verbose (bool): Display verbose output (optional) - trestle_root (str): Path to trestle root directory (optional)

Returns: str: Result summary string. On success, a checked message with output. On failure, a cross mark and error details.

Examples: - Minimal invocation trestle_author_profile_resolve(name="myprofile", output="catalog_resolved") - With options trestle_author_profile_resolve(name="myprofile", output="catalog_resolved", show_values=True, bracket_format="(.)")

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.7/5.0
Behavior3/5

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

Annotations declare destructiveHint=true and non-idempotent write behavior, and the description's mention of a required output catalog name is consistent with writing a file, so there is no contradiction. However, it never discloses the destructive trait the annotations claim — e.g. whether an existing output catalog is overwritten, whether the workspace is modified, or what permissions are needed — so it adds only partial context beyond structured data.

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?

Front-loaded summary sentence followed by Args/Returns/Examples in a predictable docstring structure, with two concrete examples that earn their space. The per-argument list partially duplicates the input schema, which is the main redundancy.

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?

The description tells the agent where the source model lives, what the required output name means, enumerates all ten option fields with types and optionality, and supplies minimal and extended examples. Combined with the existing output schema and annotations, this is sufficient to invoke the command correctly.

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?

The schema already describes each nested field, but the description adds value the schema lacks: where the profile name is resolved from (profiles/<name>/profile.json), which fields are required versus optional, and worked examples showing bracket_format syntax like "(.)". The only gap is that the semantics of label_prefix or value_assigned_prefix remain thin beyond their schema one-liners.

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 opening sentence states a specific verb and resource: resolving an OSCAL profile into a resolved profile catalog, and even pinpoints the source location (profiles/<name>/profile.json). It is clear what the tool does, though it does not differentiate itself from the sibling assemble/generate tools that also transform profile-related artifacts.

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?

Usage is implied by the example invocations and the requirement that the profile already exist in the workspace, but there is no explicit statement of when to use this versus trestle_author_profile_assemble or trestle_author_profile_generate, and no stated prerequisite that the profile must be assembled first.

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