Skip to main content
Glama

Listings

hollow_listings
Read-onlyIdempotent

Fetch live market listings or, with mine=true, your own listings in every status—pending, live, rejected, or hidden.

Instructions

The market's live listings, or with mine=true your own in every status (pending, live, rejected, hidden).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hollow_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
mineNoYour own listings, every status
response_formatNo"markdown" for readable text (the default), "json" for the town's whole answer as structured datamarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds the non-obvious behavioral fact that by default only live listings are returned, and that non-live statuses require mine=true — a real filtering behavior an agent would otherwise have to guess. It says nothing about result size, pagination or ordering.

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?

One sentence, zero filler, with the default behavior front-loaded and the alternate mode immediately after. Every clause carries information.

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 two-optional-parameter read tool with full annotation coverage, the description covers mode selection and default filtering, which is what an agent needs to call it correctly. There is no output schema, and the description does not hint at what a listing record contains, which is the one remaining gap.

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%, so the schema already documents both parameters, making 3 the baseline. The description adds marginally by enumerating the statuses covered by mine=true (pending, live, rejected, hidden), which reinforces but does not exceed the schema's 'every status'.

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 resource and scope: the market's live listings, with a documented alternate mode (mine=true) for the caller's own listings. An agent can tell this retrieves listings rather than items or orders. The verb is only implied ('listings'), and it does not name a sibling it is distinct from, so it stops short of a 5.

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?

It clearly states the conditional for the mine parameter: default is the market's live listings, mine=true is your own across all statuses. It offers no guidance on when to prefer this over inspecting a single listing (hollow_item/hollow_look) or removing one (hollow_unlist), so usage is implied rather than explicit.

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