Skip to main content
Glama

listseat_claim_status

Read-only

Unpaid lookup. Checks whether an origin has a ping-verified row on GET /verified. Returns claimed and listed only from that row. listed=true is never invented. Does not pay. Seat door is GET /api/v1/listseat at $0.09.

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": {
      "origin": "<origin>"
    },
    "name": "listseat_claim_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
originYesPublic https origin to look up. Localhost and tunnels are rejected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With readOnlyHint and openWorldHint already supplied, the description adds meaningful behavioral context: no payment is made, results come only from a ping-verified row, and listed=true is never fabricated. It does not cover auth, rate limits, or error behavior, but it discloses the key cost and data-source traits that differentiate this lookup.

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?

The definition is front-loaded and compact: it leads with 'Unpaid lookup' and then explains the check, return behavior, and paid alternative. The phrasing is telegraphic and 'Unpaid lookup' plus 'Does not pay' is mildly redundant, but no major sentence is wasted.

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 one-parameter read-only lookup with no output schema, the description gives enough to call it correctly: origin is fully documented by the schema, the data source is named, and return semantics for claimed and listed are described. It could be slightly more complete about missing-row or error behavior, but the core is covered.

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% and the sole origin parameter is already documented as a public https origin with localhost and tunnels rejected. The description does not add further meaning about the origin parameter beyond what the schema provides, so the baseline 3 is appropriate.

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?

The description states a specific verb and resource: it checks whether an origin has a ping-verified row on GET /verified. It also frames the tool as an unpaid lookup and contrasts it with the paid seat door, making its role distinguishable from a seat-purchase sibling.

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?

The description clearly signals when this tool is appropriate by calling it an unpaid lookup and noting that it does not pay, while pointing to the paid seat endpoint at GET /api/v1/listseat for $0.09. It does not explicitly name the sibling tool or spell out the exact conditions requiring the paid alternative, so it falls short of fully explicit routing guidance.

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