Skip to main content
Glama

body_roles

Lists each team role with its allowed tools, permissions, and required output so an orchestrating agent can assign and verify execution contracts.

Instructions

The team: each role's tools, permission and what it must produce.

The roles are responsibilities, not separate models - the connected agent is the orchestrator and the brain; the body executes each contract.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure. It does communicate that the tool concerns role definitions and what each role must produce, which is useful context, but it omits read-only/side-effect status, return format, and any relationship to role execution tools.

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 short and avoids bloat, but the first sentence is a fragment ('The team: ...') rather than an operational statement. The second sentence adds useful conceptual framing but does not clarify the tool's invocation behavior.

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 zero-parameter informational tool with no output schema, the description should make the returned role catalog clearer. It lists the kinds of role information available, which is helpful, but does not explain how an agent should use this with role-start/finish siblings or what invoking it actually returns.

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?

The tool has zero parameters, so there is no parameter semantics to explain beyond the schema. The baseline for zero-parameter tools is 4, and no additional parameter guidance is needed.

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 indicates the resource is 'the team' and that it covers each role's tools, permission, and expected output. However, it never states a clear operation such as listing, retrieving, or describing roles, so the exact purpose remains somewhat vague. It is distinguishable from action siblings like body_role_start, but not crisply.

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 explicit guidance on when to call this tool versus siblings such as body_role_start, body_role_finish, or body_profile. The second sentence provides conceptual context about roles being responsibilities rather than models, but it does not translate into actionable usage conditions.

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