Skip to main content
Glama

Metis — Load Tool Group

load_tool_group

Load all tools in a named group at once to prepare for several related operations, such as dataset cleaning or platform-specific work.

Instructions

Load every tool in a named group at once (see list_tool_groups for names).

Use this when you know you'll do several related operations — e.g. group
"data" for a full dataset-cleaning session, "specialist" for platform-specific work.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "group": "<group>"
    },
    "name": "load_tool_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the bulk, all-at-once expansion behavior, but says nothing about persistence (does the group stay loaded for the session?), context-window cost of loading a whole group, or what happens with an unknown group name.

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 tight sentences; the core action leads and the discovery pointer sits in a parenthetical rather than competing for attention. Every clause earns its place.

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?

An output schema exists, so return values need no explanation, and the discovery path plus examples cover most of what an agent needs. The remaining gap is operational: no statement of whether loading is reversible or what it costs in context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single `group` parameter, so the description must compensate. It usefully points to list_tool_groups as the enumeration source and offers two concrete example values, but leaves the exact format (slug vs display name, case sensitivity, failure on invalid input) ambiguous.

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?

Specific verb (load) plus resource (tool group) with an explicit bulk scope ("every tool in a named group at once"). It also distinguishes itself from the sibling list_tool_groups by naming it as the source of valid group names.

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

Usage Guidelines4/5

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

Gives a clear selection rule — use it when several related operations are anticipated — with concrete motivating examples ("data" for dataset cleaning, "specialist" for platform work). It lacks an explicit when-not / cost caveat, which would be the natural complement.

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

Deploy Server

Other Tools