Skip to main content
Glama

body_skill_list

Lists known skills with their names, goals, reasons, steps, and verification status so agents can select and apply appropriate capabilities.

Instructions

The skills we know: name, goal, why, steps and whether they were verified.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It hints at a read-only retrieval by describing the fields returned (name, goal, why, steps, verification status), but says nothing about pagination, whether results are truncated, ordering, or cost. With zero annotation coverage, this is a thin behavioral profile.

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?

One short sentence with no filler, and the returned-field list is front-loaded. The phrasing 'The skills we know' is slightly informal but not wasteful; there is no redundancy or padding.

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 simple, single-parameter list tool with no output schema, describing the fields returned is genuinely useful. Still, the omission of limit/pagination semantics leaves a real gap, since the default cap of 20 is invisible to the agent from the description alone.

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?

The single parameter 'limit' has 0% schema description coverage and a default of 20, and the description never mentions it. An agent reading only the description would not know results are capped or that it can request more, so the description fails to compensate for the schema gap.

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

Purpose3/5

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

The description conveys that this returns the catalog of known skills and enumerates the fields each entry carries, which makes the resource clear. However, it never states an explicit verb or operation ('list/retrieve all'), opening with the vague phrase 'The skills we know.' An agent can infer a read/list operation, but the purpose statement is implicit rather than stated.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: nothing tells the agent to call this before body_skill_replay or body_skill_save, nor any condition under which it should be avoided. The sibling set clearly contains related skill tools, but the description provides no routing signal between them.

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