Skip to main content
Glama

resource_bundle

DestructiveIdempotent

Groups existing resources into a bundle with usage, element mapping, short-range configuration, applicability, and license metadata for materials simulation workflows.

Instructions

Group existing resources with native usage, element mapping, short-range configuration, applicability and source license. Metadata retains file/measurement distinctions; it grants no validation by itself.

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": {
      "resource_ids": "<resource_ids>",
      "name": "<name>",
      "usage": "<usage>",
      "op_id": "<op_id>"
    },
    "name": "resource_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
op_idYes
usageYes
resource_idsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is partly known. The description never addresses the destructive aspect at all (what happens to the grouped resources, whether membership can be undone), and its only behavioral content is the caveat that metadata 'grants no validation by itself', which is useful but far too thin for a destructive mutation with four required inputs.

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?

Two sentences with no filler, and the second sentence carries the most concrete information, but the first is a dense jargon list rather than a front-loaded statement of effect. It is short without being clarifying.

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

Completeness2/5

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

Given a destructive, idempotent mutation with four required parameters (including a free-form nested object) and zero schema descriptions, the description should explain effect, undo behavior, and parameter intent. An output schema exists so return values need not be covered, but the remaining gaps are substantial.

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 carries the full burden for four required parameters, yet it never mentions resource_ids, name, or op_id. The word 'usage' happens to match the required nested 'usage' object, but no semantics (expected keys, format, relationship to applicability) are given, and op_id is left entirely unexplained despite looking like an idempotency or operation key.

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 verb-plus-resource phrase 'Group existing resources' is specific enough to identify the action, but the qualifying list ('native usage, element mapping, short-range configuration, applicability and source license') is domain jargon that does not tell an agent what the resulting grouping is or how it differs from siblings such as resource_register or resource_search. An agent would recognize the tool creates bundles but could not confidently predict its effect.

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, no prerequisites, and no reference to any alternative (resource_register, resource_get, resource_search all exist in the sibling list). The agent must infer from the name alone when bundling is the right call versus registering or fetching resources individually.

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