Skip to main content
Glama

Read one task in full

uain_tasks

Read one task in full by task_id: what it asks, its criteria and results so far. With project_id instead, list that project's tasks.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
task_idNo
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

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does disclose that this is a read operation and sketches the return payload ('what it asks, its criteria and results so far'), which is real added value, but it omits pagination behavior despite page/page_size parameters and never says what a call with no arguments returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with the primary single-task mode before the alternative. Every clause carries information; there is no filler.

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 and no annotations, the description does a reasonable job covering purpose, both access modes, and the shape of the returned content. The remaining gaps are the undocumented paging parameters and the undefined no-argument behavior, which are secondary but real for a four-parameter tool.

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 carry parameter meaning, and it does explain task_id (full task) and project_id (project listing) in functional terms. The two paging parameters are left entirely undocumented in both schema and description, and the implied exclusivity of task_id vs project_id is not confirmed against a schema that permits both.

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?

The description gives a specific verb+resource ('Read one task in full by task_id') and explicitly names the secondary mode ('With project_id instead, list that project's tasks'), so the dual behavior is unambiguous. It stops short of naming the sibling it differs from (e.g. uain_find_tasks), so an agent must infer that this is a direct-fetch rather than a search tool.

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 usefully splits usage by parameter: task_id for a single full task, project_id for listing a project's tasks. However, there is no guidance on when to prefer this over the task-search sibling, and no statement about what happens when neither parameter is supplied, even though the schema marks zero parameters required.

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