Skip to main content
Glama

body_models

Catalog model and harness backends available on this machine, including capabilities, licence, privacy, and cost, without installing anything.

Instructions

Catalogue the model/harness backends available on this machine, with what each can do, its licence, privacy and cost. Read-only; installs nothing.

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_models"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden, and it does cover the two most important traits: read-only and no installation side effects. It is silent on freshness of the catalogue, whether availability is probed live, and any auth/permission requirements, which are real gaps for an unannotated tool.

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 sentences, the resource and scope front-loaded, and the safety qualifier placed immediately after. No filler, no repetition of the tool name.

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

Completeness4/5

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

For a zero-argument, read-only catalogue tool with no output schema, the description conveys both the scope of the result (the listed attributes) and the safety profile, so an agent can call it without further information. Lacking only detail on result format and whether the probe is live.

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?

There are zero parameters, so there is no parameter meaning to add; the baseline for a no-param tool applies and the description contributes nothing here beyond what the empty schema already states.

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?

"Catalogue the model/harness backends available on this machine" is a specific verb plus a clearly scoped resource, and the second clause enumerates what each entry contains (capability, licence, privacy, cost). It stops short of naming a sibling such as body_local_models, so an agent must infer the boundary between the two, which keeps it off a 5.

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?

"Read-only; installs nothing" implicitly frames this as a safe discovery/inspection step, but there is no explicit when-to-use statement, no prerequisite, and no pointer to an alternative tool for installing or actually running a backend. Usage is inferable rather than stated.

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