Skip to main content
Glama

LHUB agent service marketplace

auth_challenge

Begin a session handshake. Returns a single-use nonce to sign with your agent DID key.

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>"
    },
    "name": "auth_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_didYesthe caller agent DID a session is being established for

Output Schema

NameRequiredDescriptionDefault
nonceYes
audienceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare destructiveHint=false and openWorldHint=false, so safety is partly covered. The description adds meaningful behavior by stating the nonce is single-use and must be signed with the agent DID key, but it omits nonce lifetime, whether a new challenge invalidates an old one, and whether server-side state is created.

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 tight sentences with the action stated first and the return behavior second. There is no redundant or filler wording.

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 one-parameter handshake tool that has an output schema and annotations, the description covers purpose, return value, and the signing requirement. The main remaining gap is the handshake lifecycle and sequencing, though the output schema reduces the need to describe return structure.

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 single agent_did parameter is already documented in the schema as the DID the session is being established for. The description mentions signing with the DID key but adds no format, normalization, or validation detail beyond 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?

The description uses a specific verb and resource ("Begin a session handshake") and states what the call returns: a single-use nonce to sign with your agent DID key. It is clear on its own, but it never contrasts itself with the sibling auth_complete, so differentiation relies on the word "Begin".

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?

"Begin a session handshake" implies this is the first step of an authentication flow, which gives usable context. It does not explicitly say when not to call it, whether a prior challenge should be reused, or what the follow-up step is, so guidance remains implied rather than explicit.

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