Skip to main content
Glama

Find User

find_user

Search for users by partial, case-insensitive username to locate the right Synology Chat user.

Instructions

Find users by (partial, case-insensitive) username, e.g. 'smith'.

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": {
      "name_query": "<name_query>"
    },
    "name": "find_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
name_queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose the matching semantics (partial, case-insensitive) and that lookups are by username rather than ID. It doesn't say whether multiple users can be returned, whether results are ranked or capped, or whether the call is a safe read — meaningful gaps for a lookup with an output schema but zero annotation coverage.

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?

A single sentence with the resource, matching rule, and example front-loaded; no filler or redundant restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter lookup with an output schema, the description covers the essentials of how to form the query; return shape is handled by the output schema. Missing only edge-case behavior (no matches, multiple matches) and any indication of read-only semantics, which the absence of annotations leaves unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% (name_query has no description), so the description has to compensate, and it does: it tells the agent the parameter is a username fragment, matched partially and case-insensitively, with a worked example. Minor gaps remain (minimum fragment length, anchoring, escaping of special characters).

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 users) plus the matching rule (partial, case-insensitive username) and gives a concrete example ('smith'). It doesn't compare against any sibling, but the listed siblings (dm_channel_for_user, get_recent_posts, etc.) perform unrelated actions, so differentiation is largely unnecessary.

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?

Usage is only implied: an agent can infer this is the lookup to use when it needs a user's identity before calling something like dm_channel_for_user. There is no explicit statement of when to prefer it, what to do with zero or multiple matches, or what to do instead if the exact username is known.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.