Skip to main content
Glama

Find Users

find_users
Read-only

Search users by partial email or name and filter by role, returning IDs, roles, names, and tags; omit the query to list initial results.

Instructions

(Admin) Busca usuarios de cualquier rol por correo o nombre (coincidencia parcial).

Devuelve eduserId, email, role, fullName y sus tags. Sin query lista los primeros limit.

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": "find_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNo
limitNo
queryNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

readOnlyHint=true already declares the safety profile, and the description usefully adds the admin-only requirement, partial-match semantics, and the default no-query listing behavior. It does not address pagination, ordering, or result-size limits beyond `limit`, and the returned-field list is redundant given an output schema exists.

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?

Three short sentences, front-loaded with the permission marker and the core action, then return fields, then the fallback behavior. The return-field enumeration is wasted space because an output schema already defines the response, but nothing else is filler.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and annotations cover read-only safety. Still, a 3-parameter search tool with 0% schema description coverage leaves the `role` filter, ordering, and pagination behavior undescribed — including whether `limit` alone or offset is needed to go deeper into results.

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

Parameters3/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: `query` is explained (email or name, partial match) and `limit` is referenced in the no-query case. The `role` filter parameter is never documented, and "de cualquier rol" is about scope rather than the enum filter, leaving an agent to infer it.

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?

Specific verb+resource: search users of any role by email or name with partial matching, plus a listing fallback when no query is given. The "(Admin)" prefix and the returned-field list make the operation unambiguous. It doesn't name a sibling such as get_user for single-record lookup, so it stops short of full differentiation.

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?

"(Admin)" signals a permission prerequisite and "Sin query lista los primeros `limit`" tells the agent what happens with an empty query, which is real usage guidance. However there is no explicit when-to-use vs. when-not guidance, e.g. that get_user should be used for a known single user id.

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