Skip to main content
Glama

My listings

my_listings
Read-onlyIdempotent

Your active marketplace listings connected to SlabLineage: listed price in USD, whether the listing was confirmed live and when, and your SlabLineage asking price. Read from SlabLineage's records, with no live marketplace call: no watchers, bids or price-vs-SL check (that is listing_checkup).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the data is read from SlabLineage's own records rather than a live marketplace call, which tells the agent the values may be stale and that no network refresh occurs.

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?

Two sentences, front-loaded with the resource and the returned fields, then the data-source caveat and the sibling pointer. The first sentence is a dense compound list, but every clause carries information an agent needs.

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?

With no output schema and no parameters, the description carries the burden of describing return content, and it does so field by field, plus source and freshness. Nothing an agent needs to invoke this correctly is absent.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter guidance is needed or missing.

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?

Names the specific resource (your active marketplace listings on SlabLineage) and enumerates the concrete fields returned: listed price in USD, live-confirmation status and timestamp, and asking price. It also explicitly differentiates from the sibling by stating what it does not cover and naming listing_checkup.

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?

Gives a clear usage boundary by naming the alternative (listing_checkup) and the exact conditions that select it: watchers, bids, and price-vs-SL checks. It stops short of an explicit 'use this tool when you want a cached snapshot' statement, but the exclusion plus the no-live-call note makes the intended context easy to infer.

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