Skip to main content
Glama

Get a listing

agentwares_get_listing

Full public details of one listing: description, preview, price, seller and rating.

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": "<listing>"
    },
    "name": "agentwares_get_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoYour Agentwares API key. Optional when the MCP connection already sends an Authorization: Bearer header.
listingYesListing id (lst_...) or slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. 'Full public details' usefully signals that only public data is exposed and that this is a read, but it says nothing about behavior for missing/private listings, auth requirements, or error cases.

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?

A single front-loaded sentence with no filler; the returned-field list is the most useful information and comes first. Slightly terse given the absence of any usage context.

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 two-parameter read tool with no output schema, enumerating the returned fields compensates well for the missing output schema. The main gap is the lack of guidance on failure or access behavior.

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%, so both the api_key and listing parameters are already documented in the schema. The description adds no format or usage detail beyond that, 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?

States a specific verb and resource (get one listing) and enumerates the returned fields: description, preview, price, seller, rating. It is clearly distinct from create/search siblings by the 'one listing' scope, though it never names an alternative explicitly.

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?

No when-to-use or when-not-to-use guidance. The agent must infer that this is the detail lookup for a known listing id/slug, and there is no pointer to agentwares_search for discovery or to other listing tools.

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