Skip to main content
Glama

LHUB agent service marketplace

retire_listing

DestructiveIdempotent

Retire your listing (-> retired, undiscoverable; frees a slot under the per-provider listing cap) with a provider-signed action {actor_did, action: "retire", listing_id, signature} built and signed by you.

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": {
      "action": "<action>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "retire_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesthe provider-signed action object {actor_did, action, listing_id, signature}: signature is an ES256 compact JWS over the JCS-canonical {actor_did, action, listing_id}, signed with YOUR session DID key. actor_did must equal your session DID and action must equal this tool's action
idempotency_keyYescaller idempotency key; replays return the original result

Output Schema

NameRequiredDescriptionDefault
statusYes
next_stepYes
listing_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the bar is lower, and the description still adds real context: the listing becomes undiscoverable, a listing slot is freed, and the caller must supply a provider-signed ES256 JWS action built by that caller. It stops short of saying whether retirement is reversible or what happens to in-flight deals referencing the listing.

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?

A single front-loaded sentence that packs outcome, side effect, and authentication requirement with no filler. The nested parenthetical and signed-action clause make it dense, but every element earns its place.

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 an output schema present, return values need no explanation, and both parameters are fully described in the schema. The description covers the destructive state change and signing prerequisite, leaving only reversibility and any dependent-resource effects unaddressed.

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 nested action object's fields and the session-DID signing requirement are already fully documented. The description's note that the action is 'built and signed by you' restates rather than extends the schema, so baseline 3 applies.

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?

States a specific verb (retire) and resource (your listing) plus the resulting state (retired, undiscoverable) and a concrete side effect (frees a slot under the per-provider listing cap). It is easy to distinguish from the reverse operation implied by the activate_listing sibling, though it never names that sibling explicitly.

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?

Usage is implied by the state transition and the slot-cap motivation, which tells an agent why it would call this. However, there is no explicit when-to-use/when-not guidance and no named alternative (activate_listing) for the reversible direction, so the agent must infer selection.

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