Skip to main content
Glama
Sign In

Roundhouse

by io.roundhouseai
OverviewDiscussionsAdmin

One capability: who offers it, and what it costs

get_capability
Read-only

Every indexed endpoint that does this job, with the market's going rate. price.spot is the call-WEIGHTED price, not the median — a median counts one wallet's forty near-identical listings as forty votes for its price. Check price.spot_basis: median means no offer reported any calls and the figure is a fallback, which does not mean the same thing as a market rate. truncated: true means the offer list is a floor.

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

Returns:

  • capability: The registry entry: the job, its priced unit, and its canonical request/response.

  • price: Going rate (spot), its basis, and the min / p25 / median / p75 / max spread.

  • stats: How many offers, distinct providers, distinct hosts, and how many were answering when last probed.

  • models: For inference capabilities: which model families are sold here, and by how many providers.

  • offers: Each endpoint, its listed price, its index against spot (100 = the going rate), and its reported 30-day demand.

  • truncated: True when the candidate read hit its cap, so the offer list is a floor rather than the whole market.

Input Schema

NameRequiredDescriptionDefault
slugYesCapability slug, from `/v0/unified`.
limitNoRows to return. Clamped to 200; values outside the range are clamped, not rejected.
probableNoInclude endpoints the matcher was not confident about. Off by default: grouping two endpoints that do different jobs invents a cheaper competitor that does not exist.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish the read-only, non-destructive, open-world profile. The description adds useful behavioral context beyond them: the underlying endpoint (`GET /v0/unified/{slug}`), that no API key is required, and that `truncated: true` means the offer list is a floor rather than the complete market.

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 purpose and then uses a structured 'Returns' section. It is somewhat dense, especially around price semantics, but the explanatory sentences about spot basis and truncation earn their place given there is no output schema.

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?

Because there is no output schema, the description carries the full burden of explaining return values, and it does so thoroughly: capability, price fields, stats, models, offers, and truncation are all defined. Combined with annotations covering safety and the description covering auth and endpoint details, an agent has what it needs to call and interpret the tool.

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 description coverage is 100%, so the schema already documents `slug`, `limit`, and `probable` thoroughly. The description does not add meaning to those parameters; it focuses on return fields and pricing semantics instead, making the baseline 3 appropriate.

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 clearly states the resource: every indexed endpoint offering a given capability, with market pricing. It distinguishes detail from listing implicitly through 'this job' and the singular slug requirement, but it never names `list_capabilities` or `recommend_capability_offers` as alternatives.

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 explicit when-to-use guidance, no when-not-to-use conditions, and no named alternatives among the sibling tools. The description explains how to interpret pricing fields rather than guiding tool selection.

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