Hugging Bay

recommend_specialist

Read-only

Find a hosted Bay Run specialist for a task. Availability is provisional.

Input Schema

Name	Required	Description	Default
`task`	Yes
`limit`	No
`commercial`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 28, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / limit / minimum
```
Removed value: -1
```
- removedInput schema / properties / task / maxLength
```
Removed value: -120
```
- removedInput schema / properties / task / minLength
```
Removed value: -1
```
- removedOutput schema / additionalProperties
```
Removed value: -true
```

Changed3 schema fields changedOct 26, 2026

removedInput schema / properties / commercial / description

Removed value: -"True to require recorded permission for commercial use."

removedInput schema / properties / limit / description

Removed value: -"Maximum number of returned rows; use the stated bounds."

removedInput schema / properties / task / description

Removed value: -"Task the model or service should perform."

Changed4 schema fields changedOct 10, 2026

addedInput schema / properties / commercial / description

Added value: +"True to require recorded permission for commercial use."

addedInput schema / properties / limit / description

Added value: +"Maximum number of returned rows; use the stated bounds."

addedInput schema / properties / task / description

Added value: +"Task the model or service should perform."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

AddedOct 2, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds a genuine caveat that 'availability is provisional', which tells the agent results may be incomplete, but it does not explain what provisional means in practice (e.g., unranked, possibly empty, or subject to change).

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 short, front-loaded sentences with no wasted words. The brevity is efficient, though it edges toward being too sparse rather than over-long.

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?

An output schema exists, so return values need not be described. However, for a three-parameter tool with zero schema coverage, the description omits the meaning of two parameters and any usage routing, which is a significant gap for correct invocation.

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 the description must compensate, yet it only implies that 'task' is a description of the work. The 'limit' parameter (maximum 4) and the 'commercial' boolean are completely undocumented in both schema and description, leaving the agent to guess their meaning.

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?

States a specific verb (Find) and a concrete resource (a hosted Bay Run specialist) scoped to a task. 'Bay Run specialist' is domain jargon that may not be self-explanatory, and no sibling is named for contrast, but the purpose is discernible.

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?

No guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. 'for a task' implies the required parameter but does not tell the agent when recommendation is appropriate rather than, say, find_runnable or get_agent_discovery.

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

All Hugging Bay tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?