Skip to main content
Glama
Sign In
handoff-mcp

handoff-mcp

by felkru
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

handoff_backends

Check backend install and auth readiness, quota pool, and freshness for routing. Use this when a handoff returns an auth or not-found error to diagnose and update guidance.

Instructions

Report each backend's install + auth readiness, its quota pool, and a freshness note for the routing guidance.

Call this first if a handoff returns an auth/not-found error. The output
includes a `staleness` banner reminding the maintainer to refresh the model
guidance when new models ship.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "handoff_backends"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

No annotations, but description discloses output includes a 'staleness' banner and reminds to refresh guidance. Adequately informs agent of non-obvious behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, no redundancy. First sentence gives core purpose, second gives usage trigger, third adds behavioral note. Efficiently structured.

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?

Given zero parameters and presence of output schema (mentioned in context), description covers all necessary info: what is reported, when to use, and behavioral note.

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?

No parameters, so baseline 4 applies. Schema coverage 100% trivially.

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?

States specific verb 'Report' with concrete resources: install, auth readiness, quota pool, freshness note. Distinguishes from siblings by being first call on errors.

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?

Explicitly says when to use: 'Call this first if a handoff returns an auth/not-found error.' Provides clear context and condition.

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

Deploy Server

Other Tools