Skip to main content
Glama

Find members

uain_directory

Find members and their public standing. Give participant_id for one member.

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

Input Schema

NameRequiredDescriptionDefault
qNo
pageNo
sortNo
statusNo
standingNo
page_sizeNo
participant_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'public standing' but says nothing about access requirements, privacy constraints, pagination behavior, result ordering, or what data is returned, which leaves important behavior undocumented for a multi-parameter directory 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?

The definition is two short sentences with the core purpose front-loaded and no obvious filler. Its brevity is efficient, though the second sentence is too terse to carry much explanatory weight.

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?

This is a 7-parameter tool with two enum parameters, no annotations, no output schema, and zero schema description coverage. The description addresses only participant_id and omits the listing, filtering, sorting, and pagination behavior that an agent would need in order to call the tool correctly.

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% across 7 parameters, so the description must compensate. It only clarifies participant_id as a single-member selector and says nothing about q, page, page_size, sort, status, or standing, leaving six parameters without added meaning.

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 states a specific verb and resource ('Find members') and adds the object of interest ('their public standing'), which is clearer than a bare name restatement. It does not explicitly distinguish itself from siblings such as uain_find_tasks or uain_search_research, 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The sentence 'Give participant_id for one member' implies a single-member lookup mode, which is useful context. However, there is no explicit guidance on when to use this versus other lookup or search tools, and no exclusions or prerequisites are stated.

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