Skip to main content
Glama

Find tasks you can do now

uain_find_tasks

Find research tasks across the whole catalogue, paid ones first. totalOpen is the unfiltered network total; matched is the filtered count; canTakeOnThisPage counts this page only. Use q/project to choose a cause and nextCursor/limit to see more. Each shows the contribution points (Karma) accepted work gives, what it pays in AI$, what it asks and how to take it (with nothing installed, or with the kit). Use it when the person wants to contribute; needs no key.

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

Input Schema

NameRequiredDescriptionDefault
qNoSearch task titles, project goals, criteria/KPIs and catalogue areas, for example longevity or telomere.
pageNo
limitNoRows per cursor page, default 12; page/page_size remain supported.
cursorNonextCursor from the previous result. Default 0.
statusNoopen
projectNoOnly tasks in this project id, e.g. P-OPP-00009.
page_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "nextCursor from the previous result. Default 0.",
      +  "pattern": "^(0|[1-9][0-9]{0,8})$",
      +  "type": "string"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Rows per cursor page, default 12; page/page_size remain supported.",
      +  "maximum": 50,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / project
      Added value: +{
      +  "description": "Only tasks in this project id, e.g. P-OPP-00009.",
      +  "pattern": "^[A-Za-z0-9][A-Za-z0-9._:-]{0,255}$",
      +  "type": "string"
      +}
    • changedInput schema / properties / q / description
      Previous value: -"Words to search task titles for."New value: +"Search task titles, project goals, criteria/KPIs and catalogue areas, for example longevity or telomere."
    • changedInput schema / properties / status / enum
      Previous value: -[
      -  "open",
      -  "needs_comparison",
      -  "awaiting_verification",
      -  "answered",
      -  "closed",
      -  "all"
      -]New value: +[
      +  "open",
      +  "needs_comparison",
      +  "awaiting_verification",
      +  "answered",
      +  "under_review",
      +  "closed",
      +  "all"
      +]
  2. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed1 schema field changed
    • addedInput schema / properties / q / description
      Added value: +"Words to search task titles for."
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does so reasonably: it discloses result ordering, the distinction between totalOpen/matched/canTakeOnThisPage, and that no key is required for access. It leaves out rate limits, whether results are eligibility-filtered per person (implied by the title but not the body), and the default status=open scoping of results.

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 ordering, and the dense field-semantics sentence earns its place because there is no output schema. The final clause packs two unrelated facts ('wants to contribute; needs no key') into one semicolon fragment, which reads slightly run-on.

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?

For a 7-parameter list tool with no annotations and no output schema, the description compensates by documenting return fields, but omits the important fact that results default to status=open only — an agent could wrongly conclude the catalogue has no closed/completed tasks. The cursor-vs-page duality is also left unresolved.

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 coverage is 57%, in the middle band. The description adds meaning for q and project ('choose a cause') and explains cursor/limit as 'see more', but says nothing about the status enum defaulting to open, nor about page/page_size versus cursor pagination — an ambiguity the schema only partly resolves by noting page/page_size 'remain supported'.

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 — 'Find research tasks across the whole catalogue' — plus an ordering rule ('paid ones first'). It doesn't explicitly differentiate itself from the similarly named sibling uain_tasks or from uain_search_research, so an agent must infer the boundary.

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 a clear activation condition ('Use it when the person wants to contribute') and a prerequisite ('needs no key'). It does not state when NOT to use it or name an alternative for narrower searches, so the exclusions half of the guidance is missing.

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