Skip to main content
Glama

Get the signer (nothing to install)

uain_signer
Read-onlyIdempotent

Get the short signer your AI runs in its own code sandbox, so the person installs nothing: it makes the member key, signs each request for uain_member_request and checks every prepared step before signing it. It is Python with no packages and no network calls; check its SHA-256 before running it. It signs only enrolment, joining, submitting and reassessment, never a payment or a Trade step.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "uain_signer"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive), and the description adds real context beyond them: the artifact has no packages and makes no network calls, its SHA-256 should be verified before running, and its signing scope is limited to enrolment, joining, submitting and reassessment. The explicit 'never a payment or Trade step' boundary is exactly the kind of behavioral limit an agent needs. Minor tension with openWorldHint=true (the tool fetches an external artifact) but that is not a contradiction of the description's claim about the script itself.

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?

Front-loaded with the outcome (get the signer, person installs nothing) and then the supporting facts in order of importance: what it does, what it is, how to verify it, what it will not sign. The single long sentence in the middle is dense but every clause carries information. Slightly compressed rather than padded.

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?

With no output schema, the description must explain what comes back, and it does: a short Python script, package-free, no network calls, verifiable by SHA-256, with a stated signing scope. What is left implicit is the delivery mechanism (inline text vs. file path) and roughly how the agent should deploy the script, which would fully close the loop for a zero-param tool of this kind.

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?

The tool takes no parameters, so there is nothing the description could add beyond confirming a zero-argument call, and the schema already enforces additionalProperties=false. Baseline 4 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?

States a concrete action ('Get the short signer') and describes the artifact: a Python script the AI runs in its own sandbox that holds the member key and signs requests. It even names the sibling it feeds ('uain_member_request'), so an agent can place it in the workflow. What it does not say explicitly is the return shape — that the tool hands back source code rather than performing signing itself — which leaves a small ambiguity.

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?

Usage is implied rather than stated: the signer exists so 'the person installs nothing' and signs requests for uain_member_request and checks steps before signing. There is no explicit 'call this before/with X' instruction and no statement of when not to use it, though the closing line does carve out exclusions (never a payment or Trade step), which is a partial substitute.

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