Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

catalog_discover

Read-only

Discover bounded Hugging Face repository candidates with budget and cursor controls before source registration. Check access, license, and layout facts; it does not enable libraries or run models.

Instructions

Discover bounded HF repository candidates, not enabled libraries. No models, conversion or simulation; review access/license/layout facts before registering a source.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "catalog_discover"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
budgetNo
cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and network profile is covered without the description. The description does add useful context that results are candidate repositories, not usable libraries, and that license/access/layout facts must be reviewed before registering. It says nothing about pagination behavior or the meaning of the returned candidate set relative to the 'budget' parameter, which leaves real behavioral gaps.

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?

Two sentences, purpose front-loaded, with the scope exclusions following immediately. Very little waste, though the dense shorthand ('bounded HF repository candidates') costs some clarity for its brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter, open-world discovery tool with no output schema and no annotation-level parameter detail, the description should explain how to form a query and how paging/budget constrain results. It instead covers only conceptual scope, leaving an agent unable to call it confidently beyond passing a bare query string.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so all three parameters (query, budget, cursor) carry no structured explanation at all. The description compensates only indirectly: 'bounded' hints that budget limits result volume, and the whole framing implies a discovery/paging flow, but query syntax, what the budget object accepts, and how cursor paging works are never addressed. With zero coverage, this is a substantial shortfall.

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 states a concrete verb and resource ('Discover bounded HF repository candidates') and explicitly bounds the scope with 'not enabled libraries' and 'No models, conversion or simulation.' An agent can tell this is a pre-registration discovery step rather than a search or acquisition call, though the abbreviation 'HF' and the modifier 'bounded' are unexplained jargon that keep it from being fully self-evident.

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

Usage Guidelines3/5

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

It gives an exclusion set ('no models, conversion or simulation') and a workflow cue ('review access/license/layout facts before registering a source'), which implies this runs before source registration. However, it never names the obvious alternative (catalog_search) or states the condition that would select one over the other, so the routing decision is left to inference.

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