Skip to main content
Glama
Sign In
MCP Server for OSCAL

MCP Server for OSCAL

by dfkunstler
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_mapping_collections

Lists loaded OSCAL Mapping Collections with UUID, title, child count, and size to help pick a query_value for query_mapping_collection. Results are paged.

Instructions

List loaded OSCAL Mapping Collections with UUID, title, child count, and size. Use when picking a query_value for query_mapping_collection. Results are paged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum items per page, 1-100.
offsetNoZero-based index of the first item.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.7.1
    • addedInput schema / properties / limit / description
      Added value: +"Maximum items per page, 1-100."
    • addedInput schema / properties / offset / description
      Added value: +"Zero-based index of the first item."
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the full disclosure burden. It usefully reveals that only *loaded* collections are returned and that results are paged, but says nothing about permissions, ordering, or whether loading state can change between calls — relevant for a registry-listing tool with an explicit 'loaded' qualifier.

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?

Two sentences, zero filler: the first describes the return payload, the second the selection criterion and pagination. Both front-load the information an agent needs before invoking.

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?

With no output schema, the description compensates by enumerating the returned fields, and it notes pagination so the agent knows to handle limit/offset. Only ordering of results and behavior when no collections are loaded are left unstated.

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 100% with both limit and offset documented, including ranges and defaults, so the schema does the heavy lifting. "Results are paged" corroborates the parameters but adds no syntax or constraints beyond what the schema already states. Baseline 3 applies.

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?

States a specific verb and resource plus the exact fields returned (UUID, title, child count, size), which lets an agent anticipate the shape of results. It does not explicitly distinguish itself from the near-named sibling list_mapping_collection_mappings, but naming query_mapping_collection as the downstream consumer clarifies its role.

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?

"Use when picking a `query_value` for query_mapping_collection" gives a concrete selection criterion and names the alternative tool it feeds. It stops short of stating when NOT to use it (e.g., if the UUID is already known) but the usage context is unambiguous.

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