Skip to main content
Glama

Search proposed projects

uain_proposals
Read-onlyIdempotent

Search the 21,600 proposed projects (ideas not yet funded or started), or read one by id. Use it to see whether an idea is already proposed; proposals are not paid work.

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

Input Schema

NameRequiredDescriptionDefault
idNo
pageNo
domainNo
searchNo
pageSizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new context: the corpus size (21,600), the lifecycle stage of records (not yet funded or started), and the caveat that proposals are unpaid. It says nothing about result shape or pagination behavior, which the schema only partly implies via the pageSize cap of 24.

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 sentences with no filler. The scope and the read-by-id path are front-loaded, and the lifecycle clarification arrives exactly where it prevents confusion.

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?

There is no output schema, so the description is the only place an agent could learn what a result looks like, and it offers nothing. Combined with fully undocumented parameters, notably the unexplained 'domain' filter, the definition is not complete enough for an agent to invoke this tool confidently beyond a bare keyword search.

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%, so the description must carry parameter meaning. It explains only that 'id' reads a single record and that the tool searches; 'domain' (max 200 chars, no format hint), 'page', and 'pageSize' are left entirely unexplained in both schema and description. For a five-parameter tool with zero structured documentation, this is a substantial gap.

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 ('Search the 21,600 proposed projects ... or read one by id') and adds the disambiguating definition '(ideas not yet funded or started)', which separates it from the sibling uain_projects. It stops short of naming an alternative tool, but the resource definition itself does the differentiating work.

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?

'Use it to see whether an idea is already proposed' gives one concrete when-to-use scenario, and 'proposals are not paid work' warns the agent off a likely misread. There is no when-not-to-use guidance and no pointer to a sibling for adjacent needs such as funded work, so usage is implied rather than bounded.

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