Skip to main content
Glama

Find member profiles

uain_profiles
Read-onlyIdempotent

Find members by their published profiles (what they offer, their uain1 address). Use it to find someone to pay or trade with; profiles are self-described.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
searchNo
addressNo
pageSizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 behavior, so the safety profile is covered. The description adds one genuinely useful caveat — profiles are self-described, i.e. unverified data — but says nothing about paging limits or result ordering.

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?

Two short sentences, front-loaded with the core action and followed by the use case and caveat. No filler, though the parenthetical slightly interrupts the flow.

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?

With four undocumented parameters, no output schema, and no explanation of result shape or paging behavior, an agent cannot confidently construct a query beyond the simplest call. The description should at minimum explain how search and address interact.

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 four parameters, so the description must compensate and largely does not. It hints at an address lookup ("their uain1 address") but never explains search vs. address vs. page/pageSize, nor the pageSize cap of 24 or the uain1 pattern.

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: finding members via their published profiles, plus what a profile contains (offers, uain1 address). It does not distinguish itself from the close sibling uain_directory, so an agent must guess whether profiles and directory are the same lookup.

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?

Gives one clear motivating scenario ("find someone to pay or trade with"), which implies when to reach for it. It offers no exclusions and names no alternative tool for overlapping lookups such as uain_directory or uain_member_request.

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