Skip to main content
Glama

Read projects

uain_projects

Read research projects: their goal, members and tasks. Give project_id for one project, with list "tasks" or "members" for its rows.

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

Input Schema

NameRequiredDescriptionDefault
qNo
listNo
pageNo
sortNo
statusNo
page_sizeNo
project_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?

With no annotations supplied, the description carries the full behavioral burden; 'Read' implies a non-destructive operation and it discloses the returned fields. It says nothing about pagination despite page/page_size existing, nor about permissions, result size, or how list interacts with project_id, so the disclosure is partial for a 7-parameter read tool.

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 sentences, front-loaded with purpose then the mode-selection rule; nothing is padding. The second sentence is slightly garbled ('with list "tasks" or "members" for its rows'), costing a point on clarity but not length.

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?

Seven parameters, zero schema descriptions, no annotations, no output schema — the description covers only two of the parameters and inaccurately enumerates one enum. An agent cannot tell from this text what q, sort, status, or the pagination fields do, which is a substantial gap for a tool of this complexity.

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 description coverage is 0%, so the description must compensate, and it only explains project_id and list. Worse, it says list accepts "tasks" or "members" while the enum also includes "claims", so an agent relying on the prose would miss a valid value. The five remaining parameters (q, page, page_size, sort, status) are left entirely to the 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?

States a specific verb and resource ('Read research projects') and names the payload ('goal, members and tasks'), which tells an agent what comes back. It also distinguishes the two modes (all projects vs. one project via project_id), though it never names a sibling such as uain_tasks or uain_search_research to route against.

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?

It gives a conditional invocation rule — supply project_id for a single project, add list "tasks"/"members" to expand its rows — which is real usage guidance. It stops short of when to prefer this over uain_tasks, uain_find_tasks or uain_search_research, so the choice among siblings is left to inference.

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