Skip to main content
Glama

List Reconstruct skills

list_skills
Read-onlyIdempotent

Discover Reconstruct workflow skills when the task's workflow is unknown. Read the selected instructions with get_skill using skill://reconstruct/ plus the returned path. For building an already selected interface load reconstruct-build only; its optional offline scene_reader helper provides bounded scene queries. Load inspect/design/verify separately only when their distinct task is needed. Remote servers add archive.url, an absolute download URL for each skill ZIP. This tool works in clients without MCP resources/read.

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

No arguments

Output Schema

NameRequiredDescriptionDefault
skillsYes
versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +true
    • removedOutput schema / description
      Removed value: -"Structured result. Existing text or image content remains available in content."
    • removedOutput schema / properties / result
      Removed value: -{
      -  "additionalProperties": true,
      -  "properties": {
      -    "skills": {
      -      "items": {
      -        "additionalProperties": true,
      -        "properties": {
      -          "description": {
      -            "type": "string"
      -          },
      -          "name": {
      -            "type": "string"
      -          },
      -          "path": {
      -            "type": "string"
      -          },
      -          "resources": {
      -            "type": "array"
      -          }
      -        },
      -        "required": [
      -          "name",
      -          "path",
      -          "description",
      -          "resources"
      -        ],
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    "version": {
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "version",
      -    "skills"
      -  ],
      -  "type": "object"
      -}
    • addedOutput schema / properties / skills
      Added value: +{
      +  "items": {
      +    "additionalProperties": true,
      +    "properties": {
      +      "description": {
      +        "type": "string"
      +      },
      +      "name": {
      +        "type": "string"
      +      },
      +      "path": {
      +        "type": "string"
      +      },
      +      "resources": {
      +        "type": "array"
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "path",
      +      "description",
      +      "resources"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / version
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "result"
      -]New value: +[
      +  "version",
      +  "skills"
      +]
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real context beyond them: remote servers append an absolute archive.url per skill ZIP, and the tool works in clients lacking MCP resources/read. It does not describe ordering or result-set size, but with safe-read annotations covering the risk profile and an output schema covering the response shape, this is solid disclosure.

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?

Purpose and the get_skill follow-up are front-loaded before the conditional guidance, which is the right order. It is dense, though: the scene_reader aside and the client-compatibility note could arguably live with the build skill's definition, adding minor drift to an otherwise tight five sentences.

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 covers the full invocation path (list, then read via skill://reconstruct/ plus the returned path), the extra field on remote servers, and a fallback for clients without resources/read. With an output schema present, return values need no further explanation and nothing an agent needs to call this correctly is missing.

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 tool takes zero parameters, so the baseline is 4; the description's mention of archive.url describes a returned field rather than an input, which is consistent but adds nothing to parameter semantics. Nothing further is required here.

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 opens with a specific verb+resource ('Discover Reconstruct workflow skills') plus a triggering condition ('when the task's workflow is unknown'), and it immediately distinguishes itself from the sibling get_skill, which is named as the reader of the returned paths. An agent can tell what this does and what it is not without opening any schema.

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

Usage Guidelines5/5

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

Explicit when-to-use rules are given for each branch: this tool when the workflow is unknown, reconstruct-build only for an already selected interface, and inspect/design/verify only when their distinct task is needed. That is when/when-not plus named alternatives, not implied usage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources