Skip to main content
Glama

Read published research

uain_contributions

Read the archive of research members have published, with its checks and the awards paid; give contribution_id for one in full. For one member's current points and accepted answers, use uain_contribution. Your own submissions and their review outcomes are read signed with your key, through uain_member_request (nothing installed) or the kit's history.

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

Input Schema

NameRequiredDescriptionDefault
qNo
pageNo
sortNo
statusNo
page_sizeNo
project_idNo
contribution_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

B3.3/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 burden. It makes clear this is a read of a public archive and, by contrast, implies that signed/authenticated reads belong to a different tool (uain_member_request). It says nothing about pagination, result ordering, rate limits, or the shape of the response.

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?

Three tight sentences, purpose front-loaded, followed by sibling routing. Little waste, though the telegraphic phrasing ('with its checks and the awards paid') is cryptic enough to cost a bit of clarity.

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

Completeness2/5

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

A 7-parameter, zero-required listing tool with no annotations, no output schema, and no schema descriptions gets only one parameter's behavior explained. An agent cannot determine what filtering, sorting, or paging behavior to expect, or what the returned records contain.

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 0% across 7 parameters, so the description must compensate and largely does not. It only explains contribution_id (returns one entry in full); q, page, page_size, sort, status, and project_id go entirely undocumented, including the five sort enum values and the meaning of status.

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 specific verb and resource: reads the archive of research members have published, including its checks and awards paid. It also distinguishes two modes (list vs. 'give contribution_id for one in full') and names the sibling it is not (uain_contribution). Domain jargon like 'checks' is unexplained, keeping it from a 5.

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?

Gives explicit routing: use uain_contribution for one member's current points and accepted answers, and uain_member_request (or the kit's history) for your own submissions and their outcomes. It also says to pass contribution_id to fetch a single entry in full. It never addresses the likely alternative uain_search_research, so the exclusion set is incomplete.

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