Skip to main content
Glama
Sign In
OpenConstruction MCP

OpenConstruction MCP

by Ben11304
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

List OpenConstruction skills

list_skills

List OpenConstruction skills metadata defined in the repository, optionally filtered by lifecycle stage.

Instructions

List repo-defined OpenConstruction skill metadata.

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

Input Schema

NameRequiredDescriptionDefault
lifecycle_stageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It signals a non-mutating list operation and the word 'metadata' is helpful, but it does not disclose the output structure, whether all skills or only a filtered subset are returned, or any pagination/ordering behavior.

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 description is one short, front-loaded sentence with no unnecessary details. It loses one point because much of the text simply restates the title rather than adding substantive behavioral or contextual value.

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

Completeness2/5

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

With no output schema and no annotations, the description is too thin to be considered complete. It would be materially better with a sentence about returning all repo-defined skills by default, optionally filtering by lifecycle_stage, and using get_skill for full details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverageand the tool description never mentions lifecycle_stage. The enum and parameter name are self-descriptive, but the description does not compensate for the lack of schema documentation, leaving the effect of lifecycle_stage implicit.

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 states a clear verb ('List') and a specific resource ('repo-defined OpenConstruction skill metadata'), so an agent can see this is a collection-returning operation and not a single-skill getter. It does not explicitly mention the sibling get_skill, but the phrase 'repo-defined skill metadata' provides enough distinction for basic identification.

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?

There is no guidance about when to call this tool versus get_skill, search_resources, or the other siblings. The description also does not say whether lifecycle_stage is an optional filter or make clear the point at which listing skills is the right step.

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