sa-ecosystem-node

List listings

list_listings

Read-onlyIdempotent

Read signed business listings from the pinned hub store, filter by stream, category, or status, and include expired rows only when needed; each result shows signer and signed meaning.

Instructions

Read signed business listings from the pinned hub store. Filter by stream, category, or status. Expired listings are hidden unless includeExpired is true, and those rows are marked expired. Each listing includes the signer's display name and a plain signedMeaning line. The url is the business's own page. This node does not take payment. Signer, threshold, revocation, and manifest-pin checks match hub_updates. Read-only.

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": "list_listings"
  }
}

Input Schema

Name	Required	Description
`status`	No	available, sold_out, inquire_only, or paused. withdrawn is a takedown and those rows are left out.
`stream`	No	referral, hybrid, irl, or player.
`category`	No	One list_categories id.
`includeExpired`	No	When true, include listings whose expiresAt is before today (UTC) and set expired to true.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 4, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the bar is lower, yet the description still adds real context: expired rows are hidden by default and flagged expired when included, withdrawn rows disappear, signer and signedMeaning are surfaced, and verification semantics match hub_updates. It also discloses 'does not take payment', which is a useful behavioral boundary.

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?

Front-loaded with the core action, then filters, then return shape, then trust/behavior notes. Every sentence carries something, though 'Read-only.' is somewhat redundant against readOnlyHint and the verification sentence is dense.

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?

With no output schema, the description usefully names the returned fields (signer display name, signedMeaning, url, expired marker) and covers the trust model. Coverage is solid for a 4-param read tool; only a note on result size or ordering is missing.

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% with three enums, so the schema carries the parameter burden. The description only restates the includeExpired default-hidden behavior and confirms url points at the business's own page, adding little beyond the structured field text.

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?

States a specific verb and resource ('Read signed business listings from the pinned hub store') plus the filter dimensions, which lets an agent separate it from siblings like hub_updates, search_hub, and list_categories without opening the schema.

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 implies when to use the tool (browsing signed listings, filtering by stream/category/status) and points at list_categories for category ids, but never states exclusions or explicitly names an alternative such as search_hub for keyword lookups.

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