Skip to main content
Glama

Read a listing's packet manifest

get_asset_manifest
Read-only

Read the canonical asset manifest (sha256-stamped).

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_asset_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.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that the manifest is canonical and sha256-stamped, which usefully signals content integrity and authority. It does not disclose what happens if a listing has no manifest, whether the manifest is static or regenerated, or anything about size/pagination.

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?

A single short sentence with the key qualifier ('canonical', 'sha256-stamped') in parentheses. Nothing wasted and no burying of the important detail.

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 one required parameter and annotations covering safety, the definition is nearly sufficient, but there is no output schema and the description never says what a manifest contains (file list, hashes, sizes?) or how it differs from the bundle and agent-commerce manifests. For a lookup tool whose entire value is the returned structure, that is a meaningful omission.

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 description coverage is 100% and the single listing_id parameter is documented in the schema as a UUID 'as search returns it', so the schema carries the parameter burden. The description adds no meaning about the identifier beyond what the schema states; 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?

The description names a specific verb and resource ('Read the canonical asset manifest') and adds a qualifier ('sha256-stamped') that tells the agent this returns authoritative, integrity-verifiable data. It does not, however, differentiate itself from close siblings like get_bundle_manifest or get_agent_commerce_manifest, so the agent must infer which manifest applies to a listing.

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 guidance on when to call this versus get_asset, get_bundle_manifest, or get_agent_commerce_manifest, and no stated prerequisites. With four manifest-adjacent siblings, the absence of any routing hint is a real gap.

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