Skip to main content
Glama
roynertr

COBie MCP

by roynertr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_runtime_skills

List all available runtime skills in the COBie MCP server, returning their names, descriptions, and version hashes for orchestration and routing.

Instructions

List available runtime skills for orchestration (agentic affordance).

Returns name, description, version_hash for each skill. Use get_runtime_skill(name)
for full body; suggest_runtime_skill(user_intent, state) to route user intent
(e.g. pending_preview_id + 'confirm' → applying-updates).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.5/5.0
Behavior3/5

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

No annotations provided. The description implies a read-only listing operation and states the returned fields, but does not explicitly declare side-effect-free behavior or permissions, placing some burden on the agent.

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 concise sentences. Purpose is front-loaded, followed by return details and routing guidance. No wasted words.

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?

With no parameters and a simple listing purpose, the description is complete. It specifies the key returned fields and points to related tools, covering everything needed for correct invocation.

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?

Tool has zero parameters, so baseline score of 4 applies. No parameter semantics needed; description covers the output.

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?

Clearly states it lists available runtime skills for orchestration, specifying the resource (runtime skills) and the action (list). Distinguished from sibling get/suggest skills by focusing on enumeration.

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?

Explicitly instructs when to use this tool versus get_runtime_skill and suggest_runtime_skill, including an example for routing user intent. No ambiguity about alternatives.

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