Browse RunningHub models by category—image, video, audio, or other—and filter by group to find models for your generation task.
按类别浏览 RunningHub 模型目录。category=image|video|audio|other。
| Name | Required | Description | Default |
|---|---|---|---|
| group | No | 可选分组过滤 | |
| limit | No | 返回条数上限 | |
| category | Yes | 模型类别 |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, so the description carries the full burden. It doesn't disclose read-only safety, pagination behavior (despite limit default 40), rate limits, or authentication needs. 'Browse' weakly implies a read, but no behavioral traits beyond the schema are provided.
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?
Two short sentences, front-loaded with the core action. The second sentence duplicates the category enum from the schema, so it doesn't fully earn its place, but there's no filler text.
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?
With no annotations and no output schema, the definition should do more to explain what is returned, how pagination works, and when to choose this over search_models. The description leaves those gaps.
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 100%, so the baseline is 3. The description repeats the category enum already defined in the schema and adds no semantics for group or limit.
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?
States a specific verb (browse) and resource (RunningHub model catalog) scoped by category. It implicitly contrasts with search_models by emphasizing category browsing, but never names the sibling or the query-based alternative.
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?
Provides no when-to-use guidance, no exclusions, and does not mention the sibling runninghub_search_models. The only routing signal is the word 'browse', leaving the agent to infer that this is for enumeration rather than keyword search.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.