Skip to main content
Glama
nexus-xyz

nexus-exchange-mcp

Official
by nexus-xyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

login

Sign in with an EVM wallet to get a 24-hour session token used as a Bearer credential for Nexus Exchange API calls.

Instructions

Sign in with an EVM wallet to get a 24h session token. Submit an EIP-191 personal_sign signature over the exact message "Sign in to Nexus Exchange", made in the wallet and passed as signature. Omit signature to have the stdio server sign with its own wallet (see create_wallet; play-funds targets only). The returned token is the Bearer credential for the *_api_key tools. The stdio server keeps it for the rest of this session and saves it for this network in the Nexus CLI config (saved_to names the file), so nothing has to be copied into the environment. No credentials needed to call this.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageNoSigned message. Must be exactly "Sign in to Nexus Exchange" (the default if omitted).
signatureNoEIP-191 personal_sign hex (0x-prefixed, 65 bytes) over the login message. Omit it to have this server sign with its own wallet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.0
    • changedInput schema / properties / signature / description
      Previous value: -"EIP-191 personal_sign hex (0x-prefixed, 65 bytes) over the login message."New value: +"EIP-191 personal_sign hex (0x-prefixed, 65 bytes) over the login message. Omit it to have this server sign with its own wallet."
    • changedInput schema / required
      Previous value: -[
-  "signature"
-]New value: +[]
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden: EIP-191 personal_sign over the exact login message, optional server-wallet signing limited to play-funds, returned Bearer token for *_api_key tools, and session/CLI config persistence via saved_to. This is rich, actionable transparency.

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?

Six sentences, front-loaded with the login outcome, then signing instructions, token usage, and persistence behavior. Each sentence earns its place without repetition.

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 login tool with no annotations and no output schema, it covers credential requirements, signature generation, token use, session persistence, and network-specific config saving. An agent has enough information to invoke it correctly.

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?

Schema coverage is 100%, so baseline is 3. The description adds meaningful semantics beyond the schema: exact message requirement, EIP-191 signing workflow, and the consequence of omitting signature, though the schema already documents both parameters.

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 and resource: 'Sign in with an EVM wallet to get a 24h session token.' It also distinguishes the returned token's role for the *_api_key tools, making the tool's purpose self-contained among credential-related siblings.

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?

Explains how to call with or without a signature and notes that no credentials are needed. It names create_wallet for server-side signing and limits that path to play-funds targets, but does not explicitly contrast login with alternatives such as get_ws_token.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools