Skip to main content
Glama

Get Open Listing

get_open_listing
Read-only

One fan listing on XP open to offers, by the identifier from list_open_listings -- 'tell me more about those tickets'. Returns the full listing record; buy_listing_now buys it at its asking price. Requires sign-in and the read:bids scope.

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": {
      "identifier": "<identifier>"
    },
    "name": "get_open_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
identifierYesPublic listing identifier from list_open_listings.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description adds two things they cannot: an authentication requirement ('Requires sign-in') and a specific scope ('read:bids scope'). That scope detail is genuinely useful for predicting authorization failures; the only omission is whether the listing can change or expire between calls.

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?

Three short sentences, front-loaded with what is returned, then the purchase alternative, then the authorization prerequisites. The quoted user-phrase works as a compact intent example rather than filler, and nothing repeats the schema or title verbatim.

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

Completeness5/5

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

For a single-parameter read with an output schema, a complete definition needs purpose, the source of the ID, the sibling alternative, and auth/scope. All four are present, and return structure is correctly left to the output schema.

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

Parameters4/5

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

Schema coverage is 100% for the single parameter, so the baseline is 3, and the description earns an extra point by stating where the identifier comes from ('from list_open_listings'). That provenance is the one piece of semantic context the schema cannot supply, though no format or validity example is given.

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?

The description names a specific verb ('get'/'returns the full listing record'), the exact resource ('one fan listing on XP open to offers'), and the keying mechanism ('by the identifier from list_open_listings'). It also distinguishes itself from the sibling that acts on the same object, buy_listing_now, so an agent can tell the two apart without opening either schema.

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?

It gives a concrete usage scenario ('tell me more about those tickets') and names the alternative when the intent is to purchase ('buy_listing_now buys it at its asking price'). It does not explicitly exclude other retrieval siblings such as check_listing or get_ticket_listings, but the contextual routing is clear enough to act on.

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