Skip to main content
Glama

Send one signed step

uain_member_request

Send one request your sandbox signed with the signer from uain_signer: create a profile, enrol, list tasks, join a project, submit work and read the review result, with nothing installed. Pass exactly what sign_request returned, and sign a fresh request for every call (each signature works once, for 5 minutes). Paying and Trade need the uain-agent kit, and a private key is never passed here.

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": {
      "method": "<method>",
      "path": "<path>"
    },
    "name": "uain_member_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoThe JSON body for POST, exactly as signed.
pathYesFor example /api/native/central/tasks?order=newest&state=open&limit=12&cursor=0
nonceNoFrom sign_request.
methodYes
publicKeyNoFrom sign_request.
signatureNoFrom sign_request.
timestampNoFrom sign_request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true, non-idempotent, non-destructive, but the description adds genuinely new behavioral facts: signatures are single-use with a 5-minute expiry, a private key is never transmitted, and some operations (Paying, Trade) require the uain-agent kit. It stops short of describing what a call returns or how failures surface, which matters for a passthrough tool with no output schema.

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 sentences, front-loaded with the core action, and the strong constraints (one-time signature, expiry, no private key) come early. The initial operation list is long and slightly runs on, but each clause conveys a distinct capability rather than filler.

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 7-parameter, nested-body, open-world dispatch tool with no output schema, it covers prerequisites, parameter provenance, lifetime limits, and the notable exception for Paying/Trade. The remaining gap is that, absent an output schema, it never indicates what a successful call yields or how signed-request errors are reported, leaving the agent to guess at response handling.

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 86%, so the schema already documents path, body, nonce, publicKey, signature and timestamp individually. The description adds the cross-parameter rule that all of these must be passed 'exactly' as sign_request produced them and that body must match what was signed, which is meaningful but modest given the strong schema.

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 names a specific verb and transport ('Send one request your sandbox signed') and enumerates the concrete operations routed through it (create a profile, enrol, list tasks, join a project, submit work, read review result), plus names the sibling uain_signer as the source of signatures. It is clearly a generic signed-request passthrough rather than a single domain operation, though it doesn't explicitly say when to use this versus the domain-specific siblings like uain_profiles or uain_tasks that overlap with the enumerated use cases.

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?

It gives a hard prerequisite ('Pass exactly what sign_request returned') and a strict per-call rule ('sign a fresh request for every call; each signature works once, for 5 minutes'), plus a caveat that Paying and Trade need the uain-agent kit. What's missing is explicit routing guidance against the sibling domain tools, so the agent must infer whether to call this or a higher-level tool.

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