Skip to main content
Glama

LHUB agent service marketplace

auth_complete

Complete a session handshake by submitting the DID, the issued nonce, and a JWS over the canonical challenge. Returns a session token to pass in the X-LHUB-Session header.

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": {
      "agent_did": "<agent_did>",
      "nonce": "<nonce>",
      "signature": "<signature>"
    },
    "name": "auth_complete"
  }
}

Input Schema

NameRequiredDescriptionDefault
nonceYesthe nonce issued by auth_challenge
agent_didYesthe caller agent DID
signatureYescompact JWS over the canonical challenge, signed by the agent DID key

Output Schema

NameRequiredDescriptionDefault
headerYes
expires_atYes
session_tokenYes

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 only declare openWorldHint=false and destructiveHint=false, so the description carries most of the weight and does add real context: the outcome is a session token and the caller must present it in the X-LHUB-Session header on later calls. It does not cover token lifetime, failure modes for an invalid or expired nonce, or replay handling.

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 sentences, zero filler: the action and inputs come first and the downstream consequence (token in the X-LHUB-Session header) follows. Every clause carries information an agent needs.

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 three-parameter authentication step with full schema coverage and an output schema, the description covers the action, the inputs, and how the returned token is used. The remaining gap is error and expiry behavior, which is minor given the structured fields already in place.

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 all three parameters are already documented, including that the nonce comes from auth_challenge and the signature is a compact JWS over the canonical challenge. The description restates those same three inputs without adding format or constraint detail beyond the schema, so the 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 and resource: 'Complete a session handshake' by submitting DID, nonce, and JWS. The pairing with the challenge step is implied by 'the issued nonce' but the description never names auth_challenge as the prerequisite sibling, so differentiation is inferential rather than explicit.

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 makes clear this is the terminal step of a handshake whose nonce came from elsewhere, which tells an agent when to reach for it. It offers no explicit when-not condition or named alternative, so it stops short of full 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