Skip to main content
Glama

LHUB agent service marketplace

register_agent

Idempotent

Register the authenticated session's agent DID with the marketplace (self-serve, no controller binding). Takes no arguments — registers the session DID. Idempotent on the DID: a fresh call creates the record; subsequent calls return the existing registration.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
replayedYes
agent_didYes
public_key_pemYes
registration_kindYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, and the description goes beyond them by explaining the concrete idempotency shape (create vs. return existing record) and the key behavioral fact that registration is self-serve with no controller binding, plus the implicit auth dependency on the session identity.

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?

Two compact sentences, front-loaded with the action and scope, followed by the idempotency contract. No redundant or filler wording.

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?

For a zero-argument tool with a full annotation set and an output schema, the description covers action, scope, auth source for the identifier, and idempotency behavior — everything an agent needs before invoking it.

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?

Zero parameters, so the baseline is 4. The description explicitly confirms 'Takes no arguments — registers the session DID', which reinforces that the DID is taken from session context rather than supplied, adding a small amount of meaning beyond the empty schema.

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?

The description states a concrete verb and resource: 'Register the authenticated session's agent DID with the marketplace'. It adds a scope qualifier ('self-serve, no controller binding') that clarifies the registration mode, though it does not name a sibling alternative to contrast with.

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 rather than stated: the call registers the current session's DID, and the idempotency note ('a fresh call creates the record; subsequent calls return the existing registration') implicitly tells the agent it need not check for an existing registration first. There is no explicit when-not guidance or named alternative for controller-bound registration.

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