Skip to main content
Glama

Search published research

uain_search_research

Search research members have already published, by meaning and by keyword. Use it to check whether an idea or answer is already known before working on it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "uain_search_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesWhat to look for, in plain words.
limitNo
stateNo
projectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changed
    • addedInput schema / properties / q / description
      Added value: +"What to look for, in plain words."
  3. First observed

TDQS

B3.4/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 burden, and it does disclose the hybrid retrieval mode and that the corpus is restricted to already-published research. It says nothing about result ordering, result size, whether access is permission-gated, or pagination, which matters for a search tool with no output schema.

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 short sentences with the retrieval mode front-loaded and the usage rationale immediately after. Nothing is redundant or padded.

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?

For a four-parameter search tool with no annotations, no output schema, and only quarter schema coverage, the description omits both filter semantics (especially the opaque 'state' values) and anything about what a result looks like. An agent can infer intent but not how to constrain or interpret the call.

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 only 25% – just 'q' is documented. The 'state' enum (held, contested, settled, rejected, withheld, appeal_wait, appealed) encodes a domain-specific lifecycle that is completely unexplained, and 'project' and 'limit' get no mention in the description either. The description adds no meaning beyond the bare parameter names.

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 names a specific verb and resource ('Search research members have already published') and adds the retrieval mode ('by meaning and by keyword'), which tells an agent this is a hybrid semantic+keyword search over published output. It does not explicitly differentiate itself from siblings such as uain_contributions, so it stops short of 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?

'Use it to check whether an idea or answer is already known before working on it' gives a concrete pre-work context that tells the agent when to reach for this tool. There are no exclusions or named alternatives for the case where the agent wants unpublished or in-progress work.

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