Skip to main content
Glama

glimind

by io.github.shawndei

route_task

Give a task in plain language and get the SINGLE BEST live tool to do it, ready to call: the chosen tool's verdict + reliability score, its input schema and a known-good recipe, call hints (timeout/retry), the actual connection endpoint to reach it (MCP endpoint URL or package to launch — no MCP-registry lookup needed), and whether it is FREE or PAID with the exact price and precisely how to pay (x402/USDC tools are auto-payable — pay per call with no signup; others say what's needed), PLUS a ranked fallback chain to try if it fails. It also returns bestFree (top free option) and bestValue (best price-to-quality), and steers to best value. Pass freeOnly to get only free tools, or requireAutomatable to only get tools an agent can pay for by itself. One call replaces discover_tools + check_tool_reliability + prepare_tool_call + find_alternatives. Call this at the start of a task when you don't already know which tool to use — it picks the best one and tells you exactly how to call it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskYesPlain-language description of what you want to do (e.g. 'send a slack message').
viewNo'full' (default, all fields) or 'compact' (lean, far fewer tokens — just what you need to call + fail over + pay + report).
categoryNoOptional capability category to narrow the choice.
freeOnlyNoOnly consider FREE tools (many callers want this).
fallbacksNoHow many backup tools to return (default 5, max 10).
maxPricePerCallNoCap per-call price in USD; paid tools above this are excluded.
requireAutomatableNoOnly tools an agent can pay for autonomously (free or x402/USDC) — for unattended agents that can't do a human card/OAuth signup.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / fallbacks / description
      Previous value: -"How many backup tools to return (default 3, max 8)."New value: +"How many backup tools to return (default 5, max 10)."
  2. Changed4 schema fields changed
    • addedInput schema / properties / freeOnly
      Added value: +{
+  "description": "Only consider FREE tools (many callers want this).",
+  "type": "boolean"
+}
    • addedInput schema / properties / maxPricePerCall
      Added value: +{
+  "description": "Cap per-call price in USD; paid tools above this are excluded.",
+  "type": "number"
+}
    • addedInput schema / properties / requireAutomatable
      Added value: +{
+  "description": "Only tools an agent can pay for autonomously (free or x402/USDC) — for unattended agents that can't do a human card/OAuth signup.",
+  "type": "boolean"
+}
    • addedInput schema / properties / view
      Added value: +{
+  "description": "'full' (default, all fields) or 'compact' (lean, far fewer tokens — just what you need to call + fail over + pay + report).",
+  "type": "string"
+}
  3. Changed4 schema fields changed
    • removedInput schema / properties / freeOnly
      Removed value: -{
-  "description": "Only consider FREE tools (many callers want this).",
-  "type": "boolean"
-}
    • removedInput schema / properties / maxPricePerCall
      Removed value: -{
-  "description": "Cap per-call price in USD; paid tools above this are excluded.",
-  "type": "number"
-}
    • removedInput schema / properties / requireAutomatable
      Removed value: -{
-  "description": "Only tools an agent can pay for autonomously (free or x402/USDC) — for unattended agents that can't do a human card/OAuth signup.",
-  "type": "boolean"
-}
    • removedInput schema / properties / view
      Removed value: -{
-  "description": "'full' (default, all fields) or 'compact' (lean, far fewer tokens — just what you need to call + fail over + pay + report).",
-  "type": "string"
-}
  4. Changed1 schema field changed
    • addedInput schema / properties / view
      Added value: +{
+  "description": "'full' (default, all fields) or 'compact' (lean, far fewer tokens — just what you need to call + fail over + pay + report).",
+  "type": "string"
+}
  5. Changed3 schema fields changed
    • addedInput schema / properties / freeOnly
      Added value: +{
+  "description": "Only consider FREE tools (many callers want this).",
+  "type": "boolean"
+}
    • addedInput schema / properties / maxPricePerCall
      Added value: +{
+  "description": "Cap per-call price in USD; paid tools above this are excluded.",
+  "type": "number"
+}
    • addedInput schema / properties / requireAutomatable
      Added value: +{
+  "description": "Only tools an agent can pay for autonomously (free or x402/USDC) — for unattended agents that can't do a human card/OAuth signup.",
+  "type": "boolean"
+}
  6. Added

TDQS

A4.7/5.0
Behavior5/5

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

No annotations are provided, so the description carries full burden. It comprehensively describes what the tool returns (verdict, reliability, schema, recipe, hints, endpoint, pricing, fallbacks) and its behavior (single call replacing multiple). No contradictions.

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

Conciseness3/5

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

The description is verbose and packed with details, which is informative but could be more concise. It is front-loaded with the core purpose, making it structurally acceptable, but some redundancy exists.

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 the complexity (7 params, no output schema), the description is highly complete. It covers input, output, filtering options, pricing, fallback chains, and even provides a use-case reminder. No critical gaps.

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% with descriptions, but the description adds meaning by explaining parameter effects (e.g., view options, freeOnly, requireAutomatable) and how they influence results. It goes beyond basic schema documentation.

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 states the tool's purpose: to return the single best live tool for a given task, along with all details needed to call it. It explicitly distinguishes from sibling tools like discover_tools, check_tool_reliability, etc., by noting it replaces multiple calls.

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?

The description clearly states when to use: 'Call this at the start of a task when you don't already know which tool to use'. It also mentions alternatives and filters like freeOnly and requireAutomatable, providing clear decision context.

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

All glimind toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool has a distinct, well-defined purpose: checking reliability, discovering tools, finding alternatives, getting recipes, routing tasks, etc. No two tools overlap in function.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with underscores (e.g., check_tool_reliability, route_task, watch_tool). The only minor deviation is 'how_to_use_glimind', which still follows a clear verb phrase convention.

Tool Count5/5

With 15 tools, the set is well-scoped for a comprehensive meta-layer covering discovery, reliability checking, preparation, batch routing, reporting, and notifications. Each tool earns its place.

Completeness4/5

The surface covers the full workflow of discovering, checking, preparing, calling, and reporting on tools. A minor gap is the lack of a direct 'list all tools' catalog, but the discovery tools effectively fill this need.

Resources