Skip to main content
Glama
Sign In

Roundhouse

by io.roundhouseai
OverviewDiscussionsAdmin

The capability catalogue

list_capabilities
Read-only

Every job the catalog is grouped by, with the canonical request and response each provider of that job is mapped onto — which is what lets an agent swap one endpoint for another without changing its code. Static: no market figures here, because each one costs its own catalog walk. Ask /unified/{slug} for a capability's offers and going rate. Send fields=compact when you are only choosing a capability: the full response carries both IO schemas for all of them.

Wraps GET /v0/unified. Access: no API key required.

Returns:

  • capabilities: Slug, name, group, priced unit and — on fields=full — summary and the canonical input/output fields.

  • count: How many capabilities the registry defines.

  • fields: Which shape was served: full or compact.

  • note: Where the market figures for one capability live.

Input Schema

NameRequiredDescriptionDefault
fieldsNo`compact` returns slug, name, group and unit only — enough to pick a capability, without 34 pairs of IO schemas in the payload.full

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already mark it as read-only, open-world, and non-destructive, and the description adds useful context: the data is static, no API key is required, and the compact/full choice affects payload size because the full response includes both IO schemas for all capabilities.

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 front-loaded with the core concept and then provides structured return details. It is somewhat verbose, with a few explanatory clauses that could be tightened, but most sentences provide actionable information.

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 one optional parameter, no output schema, and clear annotations, the description is complete: it covers purpose, access requirements, response shape, compact/full behavior, and where to go for market figures.

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?

Schema coverage is 100% and the enum is documented, so the schema carries most parameter meaning. The description still adds practical guidance on when `fields=compact` is preferable and what `fields=full` includes, which goes beyond the raw schema definition.

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 that this tool exposes the full capability catalogue: every job the catalog is grouped by, with canonical request/response mappings. It also distinguishes this static catalogue from per-capability offer data available via `/unified/{slug}`.

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?

It explicitly says when to use the compact form versus the full form, and it explains that market figures are not here and should be fetched from `/unified/{slug}`. This gives the agent clear routing guidance between catalogue inspection and per-capability offer lookup.

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

All Roundhouse toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources