Skip to main content
Glama

LHUB agent service marketplace

activate_listing

Idempotent

Activate your staging listing (staging -> active) with a provider-signed action {actor_did, action: "activate", listing_id, signature} built and signed by you. Owner-only; actor_did must equal your session DID.

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": "activate_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

A4.2/5.0
Behavior4/5

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

Beyond the annotations, it discloses that the operation is owner-only, requires a provider-signed action built and signed by the caller, and moves the listing from staging to active. It does not add much about failure behavior or idempotency beyond the annotation, but the auth and transition details are valuable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense sentence that front-loads the state transition and follows with the authorization and signing constraints. No wording 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 two-parameter mutation with an output schema and annotations covering idempotency and non-destructiveness, the description covers the essential state change, ownership, and signing requirements. It stops short of describing invalid-state or signature-failure behavior, but is otherwise complete.

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 schema already documents both parameters in detail. The description reinforces the action object's actor_did and signature requirements but adds little meaning beyond the structured schema.

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: activate a staging listing, with the explicit state transition staging -> active. This clearly distinguishes it from lifecycle siblings such as retire_listing and create_listing.

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?

It gives clear usage context: the listing must be in staging, and the caller must be the owner. It does not explicitly name alternatives or when-not-to-use cases, but the state-bound context is sufficient for 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