Skip to main content
Glama
GemachDAO

GDEX Trading

by GemachDAO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

generate_session_keypair

Read-only

Generate a secp256k1 session keypair for manual GDEX signing; returns only the public key unless private key disclosure is explicitly requested.

Instructions

Advanced/manual signing only: generate a secp256k1 session keypair. Prefer gdex_connect, which signs in and keeps keys on this machine. Returns only the public sessionKey unless revealPrivateKey is true.

Input Schema

NameRequiredDescriptionDefault
revealPrivateKeyNoReturn sessionPrivateKey too (it then appears in the conversation)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv4.12.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / revealPrivateKey
      Added value: +{
+  "description": "Return sessionPrivateKey too (it then appears in the conversation)",
+  "type": "boolean"
+}
  2. First observedv4.11.3

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: only the public key is returned by default, and the private key would end up visible in the conversation. A minor gap remains — it never states explicitly that the key is not persisted locally (only implied by contrast with gdex_connect) nor whether the keypair can be reused after the session.

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?

Three short sentences, zero filler, and the routing constraint ('Advanced/manual signing only') plus the preferred alternative are front-loaded. Nothing would be lost by trimming.

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?

There is no output schema, and the description does state what is returned (public sessionKey, or the private key when opted in), which is the key fact for a caller. It stops short of covering persistence or lifetime of the generated keypair, a small omission for a security-sensitive tool.

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% with a single optional boolean, and the schema already explains that revealing it puts the key in the transcript. The description restates that consequence without adding syntax or format detail, so baseline 3 applies.

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 ('generate a secp256k1 session keypair') and immediately scopes it ('Advanced/manual signing only'), which separates it from signing siblings. It also names the sibling it is not (gdex_connect), so an agent can choose without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ('Advanced/manual signing only') and an explicit preferred alternative ('Prefer gdex_connect, which signs in and keeps keys on this machine'). The tradeoff that selects the alternative is stated, not implied.

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