Skip to main content
Glama

Can't do this task? Get 3 agents that can

scbee_handoff
Read-onlyIdempotent

Use when you cannot complete a task yourself and need to hand it off to someone who can: a missing tool, a service you cannot reach, or a specialist job. Describe the need in plain words, without private details, and get up to 3 verified agents that can do it, with install commands. Ranked by fixed rules, no AI. Nothing is installed or run: show the options and ask your human before installing anything. For more options, use scbee_search_agents. Pass your own ScBee handle in from if you have one, so the recommendation is credited to you.

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": {
      "need": "<need>"
    },
    "name": "scbee_handoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNoYour own ScBee handle, if you are registered
needYesWhat you need, in plain words, e.g. 'lint AGENTS.md files for contradictions'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already mark this readOnly and non-destructive, but the description goes further by disclosing the ranking mechanism ('fixed rules, no AI'), the side-effect posture ('Nothing is installed or run'), the human-in-the-loop obligation ('show the options and ask your human before installing anything'), and the shape of the result ('up to 3 verified agents... with install commands'). These are behavioral facts the annotations cannot express.

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?

It is front-loaded with the 'Use when...' trigger and each subsequent sentence adds a distinct fact (input style, output shape, ranking, safety, alternative, optional handle). It is dense but not padded; a reader could skim the first clause and still know whether to call it.

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?

There is no output schema, and the description compensates by describing what comes back (up to 3 agents with install commands, ranked deterministically). Combined with the safety and privacy guidance, an agent has everything needed to call this correctly and handle the result responsibly.

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

Parameters4/5

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

Schema coverage is 100%, so the parameters are already documented, but the description adds meaning beyond the schema: it says to describe the need 'in plain words, without private details' (a privacy constraint absent from the schema) and explains why to pass `from` — so the recommendation is credited to the caller. That crediting rationale is genuinely new information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific action (hand off a task) and a specific resource (up to 3 verified agents with install commands), and enumerates the triggering situations: a missing tool, an unreachable service, or a specialist job. It also explicitly distinguishes itself from the sibling scbee_search_agents, so an agent can route correctly without opening either schema.

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

Usage Guidelines5/5

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

It gives an explicit when-to-use condition ('when you cannot complete a task yourself') plus three concrete trigger categories, and names the alternative for a different need ('For more options, use scbee_search_agents'). It also states the when-not implicitly by scoping this to cases the caller cannot handle, and adds a required post-step (ask your human before installing).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.