Skip to main content
Glama

Finish sign-in

auth_verify

Finishes wallet sign-in: send the exact message from auth_challenge and its personal_sign signature; returns a 24 h Bearer token for higher limits and paid tools. Free, no key. Wrong or expired message or signature: error unauthorized.

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": {
      "message": "<message>",
      "signature": "<signature>"
    },
    "name": "auth_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesThe exact message auth_challenge returned, unchanged
signatureYesIts personal_sign signature, 0x + 130 hex

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / message / description
      Added value: +"The exact message auth_challenge returned, unchanged"
    • addedInput schema / properties / signature / description
      Added value: +"Its personal_sign signature, 0x + 130 hex"
    • addedInput schema / properties / signature / pattern
      Added value: +"^0x[0-9a-fA-F]+$"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The description adds real context beyond annotations: token lifetime (24 h), cost/auth requirements ('Free, no key'), and the failure mode returning 'unauthorized' for wrong or expired message/signature. The annotations declare non-readonly, non-idempotent, non-destructive, closed-world but the description does not discuss repeatability or what happens to previously issued tokens.

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?

Two dense sentences, front-loaded with the action and inputs, then output and error behavior. The telegraphic fragments ('Free, no key.', 'Wrong or expired message or signature: error unauthorized.') are efficient, though the clipped style borders on terse.

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 2-parameter tool with no output schema, the description covers what it returns (24 h Bearer token) and the main failure mode. It omits how the token should be presented on subsequent calls (Bearer header) and token expiry/refresh handling, which would make it self-contained.

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%, and the schema itself already says the message must be the exact string auth_challenge returned and the signature is personal_sign hex. The description restates this ('the exact message from auth_challenge and its personal_sign signature') without adding format or matching details, so the schema does the heavy lifting.

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?

States a specific verb+resource ('Finishes wallet sign-in'), names the exact inputs from auth_challenge, and declares the concrete output (24 h Bearer token). It is clearly distinguishable from the sibling auth_challenge, which produces the message rather than consuming it.

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?

Effectively says when to use it: after obtaining a message from auth_challenge, with the payoff spelled out ('higher limits and paid tools') and the failure condition ('Wrong or expired message or signature: error unauthorized'). It does not explicitly say when not to use it, e.g. that unsigned calls to free tools need no token.

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