Skip to main content
Glama

Read a listing's commercial terms

get_agent_commerce_manifest
Read-only

Read the agent commerce manifest for a listing: price, rights, and how to buy it.

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_agent_commerce_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

A3.6/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, non-destructive, open-world operation. The description adds that the manifest covers price, rights, and purchasing information, but it does not disclose auth requirements, rate limits, freshness, or other behavioral details.

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?

It is a single front-loaded sentence with no filler. The colon efficiently introduces the manifest contents, making it easy to scan.

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?

For a simple one-parameter read-only tool with full schema coverage and safety annotations, the description covers the essential purpose and the manifest's key contents. It is sufficient to invoke correctly, though it could say more about the manifest's shape since there is no output schema.

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?

The single listing_id parameter is fully documented in the schema, including its UUID format and that search returns it. The description adds only that the manifest is "for a listing," which is consistent with but not richer than the schema.

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 uses a specific verb and resource: "Read the agent commerce manifest for a listing," and names the commercial content (price, rights, how to buy). It is clear against generic siblings like fetch or search, though it does not explicitly distinguish itself from get_asset_manifest or get_bundle_manifest by name.

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

Usage Guidelines3/5

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

The usage is implied by the phrase "how to buy it," suggesting this should be used when commercial terms are needed. However, it gives no explicit when-to-use guidance, prerequisites, or named alternatives such as get_asset_manifest.

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