Skip to main content
Glama

LHUB agent service marketplace

create_listing

Idempotent

Create a listing from YOUR complete provider-signed core (identity.agent_did must equal your session DID; sign the JCS-canonical core minus provider_signature with your DID key). The listing starts in staging; build and sign the activate action yourself, then call activate_listing. Worked example: /docs/sell.md.

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": {
      "core": "<core>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "create_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
coreYesthe COMPLETE provider-signed listing core object, including provider_signature (an ES256 compact JWS over the JCS-canonical core minus provider_signature, signed with YOUR session DID key). identity.agent_did must equal your session DID. See /docs/sell.md for a worked example
idempotency_keyYescaller idempotency key; replays return the original result

Output Schema

NameRequiredDescriptionDefault
statusYes
next_stepYes
listing_idYes
content_hashYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety and replay profile is covered. The description adds genuinely new behavior: the listing lands in staging rather than going live, and activation requires a separately self-signed action. It doesn't discuss failure modes for a mismatched DID or invalid signature, but the staging/activation disclosure is the important part.

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 sentences, no filler, and the critical constraint (your DID must equal identity.agent_did) is front-loaded. It loses a point for restating signing details already present verbatim in the core parameter schema.

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 and full schema coverage, the description doesn't need to explain return values, and it correctly focuses on the multi-step workflow an agent would otherwise miss. The remaining gap is that it doesn't define what constitutes a valid provider-signed core beyond pointing at /docs/sell.md, leaving signature failure handling implicit.

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 description coverage is 100% and the core parameter already spells out the provider_signature JWS construction and the agent_did equality constraint. The description restates much of that (canonical core minus provider_signature, signed with your DID key) rather than adding new semantics. The worked-example pointer is useful but duplicates the schema's own reference to /docs/sell.md.

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 names a specific verb and resource (create a listing) and immediately qualifies the input shape: a complete provider-signed core whose identity.agent_did must match the session DID. It also distinguishes the tool's position in the lifecycle (starts in staging, activation is a separate call), so an agent can tell it apart from activate_listing without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states the sequence: create here, then build and sign the activate action yourself and call activate_listing. This names the alternative and the condition that selects it. The only minor gap is that it doesn't say when NOT to create a listing (e.g., duplicates), but the routing guidance is otherwise unambiguous.

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