Skip to main content
Glama

Read a member's contribution

uain_contribution
Read-onlyIdempotent

Read one member's current contribution by uain1 address, live: contribution points (Karma), each accepted answer with its task and project, checks done for others, work still waiting for review (not counted), then AI$ earned and balance as ledger facts. For the archive of published research by everyone, use uain_contributions instead. Reads only; everything here is public.

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": {
      "address": "<address>"
    },
    "name": "uain_contribution"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe member's uain1 address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description still adds real behavioral context beyond them: 'live' signals current rather than cached data, pending-review work is explicitly 'not counted', and everything is public/no-auth. It stops short of noting ordering or volume of returned items.

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 core action and address, then a compact enumeration of returned fields, then the sibling redirect. The middle list is dense and runs long as a single sentence, but each item conveys distinct information, so there is little genuine waste.

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?

No output schema exists, and the description compensates by enumerating the returned sections in order (Karma, accepted answers, checks, pending, AI$ ledger facts), including the counting caveat. For a one-parameter read tool this leaves nothing essential unexplained.

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?

There is a single parameter and schema coverage is 100%, with the regex pattern and 'uain1 address' already documented in the schema. The description's 'by uain1 address' only restates that. Per the high-coverage baseline, a 3 is appropriate since the schema carries the parameter burden.

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 ('Read one member's current contribution by uain1 address') and then enumerates exactly what is returned: Karma points, accepted answers with task/project, checks done for others, pending review items, and AI$ earned/balance. It explicitly contrasts itself with the sibling uain_contributions, so an agent can separate the two 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?

Gives an explicit routing rule: this tool is for a single member's live contribution, while 'the archive of published research by everyone' belongs to uain_contributions. It reinforces the context with 'Reads only; everything here is public', which tells the agent no auth step is needed.

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