Skip to main content
Glama

Read a bundle's file inventory

get_bundle_manifest
Read-only

Read the per-asset bundle inventory: every delivered file with role, format, size and content hash, plus counts that name the population each one counted.

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": {
      "listing_id": "<listing_id>"
    },
    "name": "get_bundle_manifest"
  }
}

Input Schema

NameRequiredDescriptionDefault
listing_idYesThe listing's id (a UUID), as search returns it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / listing_id / description
      Added value: +"The listing's id (a UUID), as search returns it."
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint false and openWorldHint true, so the safety profile is covered. The description goes beyond them by characterizing the payload shape (per-file role/format/size/hash plus named-count semantics), which is real behavioral context. It says nothing about pagination, size limits, or failure behavior for a tool flagged open-world, which keeps it from a 5.

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 front-loaded sentence with no filler; the inventory contents come before the counts clause. The trailing phrase 'counts that name the population each one counted' is slightly convoluted and could be stated more plainly.

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?

With no output schema, describing the returned fields is necessary and mostly done, and a single fully-documented parameter covers the input side. The remaining gap is selection: nothing here explains how this manifest differs from get_asset_manifest or get_agent_commerce_manifest, which is the missing piece for an agent choosing among them.

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 100% and the single listing_id parameter is fully documented in the schema, including the UUID format and provenance (as search returns it). The description adds no further meaning about that parameter, so the baseline 3 applies.

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?

Names a specific verb (read) and resource (per-asset bundle inventory) and enumerates what the result contains: role, format, size, content hash, plus labeled counts. It is clear on its own, but it never distinguishes itself from the very close sibling get_asset_manifest, so an agent cannot tell the two apart from the text alone.

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 and no alternatives referenced, even though get_asset_manifest and get_agent_commerce_manifest sit directly beside it. An agent must infer the selection rule from sibling names rather than from anything this description states.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources