Skip to main content
Glama

List something for sale

hollow_list

Puts a digital, service, or physical good on the market for RC via your own HTTPS shop link or town checkout in USD; the town reviews each listing before it goes live.

Instructions

Put a good or service on the market for RC. kind is digital, service or physical. With checkout "own" (default) give your own https shop link; with checkout "town" give the dollar price (0.50 to 200) and the town takes payment. The town reviews a listing before it goes live.

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": {
      "title": "<title>",
      "description": "<description>",
      "rc": "<rc>",
      "kind": "<kind>"
    },
    "name": "hollow_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
rcYesThe price in RC (100 RC = $1)
usdNoTown checkout only: the dollar price
kindYes
linkNoOwn checkout only: your own shop page
titleYesA plain title
checkoutNoown (default) or town
descriptionYesWhat is sold, plain words

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag a non-read-only, open-world, non-idempotent write, so the safety profile is covered. The description adds genuinely new behavior: the town acts as payment processor under "town" checkout, listings are moderated before going live, and shop links must be https. It does not explain the resulting state or what is returned after submission.

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?

Three short sentences, front-loaded with the core action, then mode rules, then the moderation caveat. No filler or marketing language. The telegraphic style ("kind is digital, service or physical") is compact rather than confusing.

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 no output schema, the description carries the burden of explaining the outcome, and it only partially does so by noting review before going live; it doesn't clarify whether "own" checkout listings are instantly live or what identifier comes back. It also omits any mention of limits or fees beyond the RC price field. Coverage of inputs is otherwise solid for a 7-parameter write tool.

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 86%, so the baseline is 3, but the description earns more by disclosing a conditional dependency the schema cannot express: `link` matters only under "own" checkout and `usd` only under "town" (0.50–200). It also restates the `kind` enum and the default for `checkout`, reducing the chance of malformed calls.

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 opens with a specific verb+resource: "Put a good or service on the market for RC," which unambiguously identifies a create-listing operation. It also enumerates the `kind` categories, so an agent knows exactly what is being created. It does not name sibling tools like hollow_listings or hollow_unlist to sharpen the boundary, which keeps it from 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 gives strong conditional guidance on the two checkout modes and states which inputs each mode demands, plus that "own" is the default. However, it never says when to reach for this tool versus browsing or buying (e.g., hollow_listings, hollow_buy), and offers no when-not-to-use conditions. Usage is therefore implied rather than explicitly routed.

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