Skip to main content
Glama

body_recommend

Ranks installed backends by how well they fit a task’s required capabilities, such as tools, vision, audio, or structured output, without downloading or launching anything.

Instructions

Dry-run recommendation: which installed backend fits a task best, and why.

Needs: e.g. ["tools", "vision", "audio", "structured_output"]. Never downloads or launches anything - it only ranks what is already here.

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": "body_recommend"
  }
}

Input Schema

NameRequiredDescriptionDefault
needsNo
max_ram_mbNo
offline_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the key safety trait (never downloads or launches, ranks only), which is genuinely valuable, but says nothing about how scoring or ranking works, how ties are resolved, what happens with zero matching backends, or how the two filter parameters alter the outcome.

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?

Two compact sentences, front-loaded with the purpose, followed by the one parameter worth illustrating and the safety constraint. No filler or repeated information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter read-only tool with no output schema and no annotations, the description covers purpose, safety, and one parameter's value set. It is incomplete on the two filter parameters and on the shape of the returned recommendation, leaving gaps an agent would have to probe.

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 and only partially does: it gives example values for "needs" (tools, vision, audio, structured_output), which meaningfully clarifies the most important parameter. max_ram_mb and offline_only are never explained, and max_ram_mb's default of 0 has no stated semantics (unlimited? disabled?).

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 and resource: it recommends which installed backend fits a task and explains why. The word "Dry-run" plus "ranks what is already here" distinguishes it from model-installation or launch tools, though it doesn't name the closest siblings (body_models, body_local_models) explicitly.

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

Usage Guidelines3/5

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

"Dry-run recommendation" implies the pre-flight use case (pick a backend before running a task), which is useful implicit guidance. However, there is no explicit statement of when not to use it, nor any pointer to alternative tools such as body_models or body_status for related questions.

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