Return the public schema for one RunningHub catalog endpoint. Use it to inspect expected request fields before creating or validating workflow JSON; it does not verify cloud access.
Return a public schema for one catalog endpoint; it does not verify cloud access.
| Name | Required | Description | Default |
|---|---|---|---|
| endpoint | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses that the tool returns a public schema and does not verify cloud access, but omits auth requirements, rate limits, and return behavior details.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence with no wasted words. It is appropriately sized for the tool's simplicity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter tool, the description conveys the core operation. However, with no output schema and no annotations, it lacks details about endpoint format and the returned schema structure.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate for the single endpoint parameter. It identifies the parameter as a catalog endpoint but gives no format, examples, or valid value guidance.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: return a public schema for one catalog endpoint. It also adds a scoping caveat about cloud access, but it does not explicitly differentiate itself from siblings like rh_search_models or rh_get_capabilities.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied: use this to retrieve a public schema for a catalog endpoint. The negative constraint 'does not verify cloud access' is useful, but there is no explicit when-to-use, when-not-to-use, or named alternative.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.