Skip to main content
Glama
dfkunstler

MCP Server for OSCAL

by dfkunstler
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_profiles

Retrieve a paginated list of loaded OSCAL Profiles with summary metadata to explore available compliance models. Supports offset and limit for navigation.

Instructions

List loaded OSCAL Profiles with summary metadata.

Args: ctx: MCP server context (injected automatically). offset: Zero-based pagination offset (default 0). limit: Maximum items to return, 1-100 (default 10).

Returns: Page_Response dict with keys: items, total, offset, limit, hasMore.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations provided, the description carries full behavioral disclosure burden but only states the return format and pagination. It does not explicitly state the tool is read-only, whether it has side effects, or any other behavioral traits.

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

Conciseness5/5

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

The description is extremely concise, front-loading the purpose, then listing parameters and return type in a structured Docstring format, with no unnecessary words.

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?

For a simple list tool with two parameters and no output schema, the description covers purpose, parameters, and return structure. Minor omission: it does not clarify what 'loaded' implies or any access requirements.

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 description adds detailed semantics for both parameters (offset and limit) beyond the input schema, explaining pagination behavior and value ranges. This compensates 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?

The description clearly states the action ('list'), the resource ('loaded OSCAL Profiles'), and the content ('summary metadata'), distinguishing it from sibling tools like query_profile or list_catalogs.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus siblings such as query_profile or list_catalogs, nor does it mention any prerequisites or context for listing profiles.

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

Deploy Server

Other Tools