Skip to main content
Glama

Read a member's public record

uain_native_state

Read a member's public record by uain1 address: membership, licence and Karma. For AI$ earned and balance, use the kit's status.

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_native_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysNo
memberNoThe member's uain1 address.
instanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changed
    • addedInput schema / properties / member / description
      Added value: +"The member's uain1 address."
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose that the record is public and what categories of data come back, but it never states that the call is read-only, whether authentication is required for public data, or how the plural "keys" parameter behaves.

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 short clauses: the primary action first, the alternative second. Nothing is padded, and the field enumeration is compact. The only soft spot is the cryptic "the kit's status" reference, which costs a little clarity without wasting space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description must carry everything. It helpfully previews the returned fields, which partially substitutes for a missing output schema, but the undocumented "keys"/"instance" parameters and absent read-only/authorization context leave real gaps for a three-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%, leaving "keys" and "instance" documented in neither schema nor description. The description clarifies that lookup is keyed on a uain1 address, but with two of three parameters unexplained it does not compensate for the coverage gap.

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?

"Read a member's public record by uain1 address" gives a specific verb and resource, and the follow-up enumerates what the record contains (membership, licence and Karma). It is clear about scope, though its differentiation from siblings relies on the vague phrase "the kit's status" rather than a named tool.

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 states the selecting condition (lookup by uain1 address) and an explicit exclusion: for AI$ earned and balance, go elsewhere. The exclusion is weakened because the destination is described as "the kit's status" instead of a concrete tool name among the listed siblings.

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