Skip to main content
Glama
JoseAlmeida-Ploomes

Ploomes MCP Server

buscar_usuarios

Find users in Ploomes CRM using filters such as name, role, team, social media accounts, and sort results by custom order with pagination.

Instructions

    🔍 Observações:
      1. O resultado da busca é limitado a resultados por página. Você pode acessar a próxima página usando o parâmetro pagina.
      2. O parâmetro 'cargo' filtra usuários pelo nome do cargo (ex: 'Supervisor', 'Analista').
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nomeNo
cargoNo
paginaNo
equipe_idNo
ordenar_porNo
tem_facebookNo
tem_linkedinNo
usuarios_idsNo
sentido_ordenacaoNo
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It reveals pagination behavior and a filter parameter, but omits other important traits such as read-only nature, authentication requirements, rate limits, or possible side effects. The partial disclosure is insufficient for safe agent use.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (two bullet points) but lacks a clear purpose statement. While concise, it is under-specified and does not front-load the core action. Every sentence should earn its place; here, the missing purpose sentence makes the structure inadequate.

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?

Given the tool has 9 parameters, no output schema, and no annotations, the description is highly incomplete. It fails to explain return values, other filters, sorting behavior, or the meaning of boolean flags. The agent would be unable to use the tool effectively with this minimal description.

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%, so the description must compensate. It only explains two parameters (cargo and indirectly pagina) out of nine. Parameters like nome, equipe_id, ordenar_por, booleans, and usuarios_ids are left undocumented. This leaves the agent without guidance on how to use most parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description lacks an explicit statement of the tool's purpose. It starts directly with observations about pagination and a filter, but does not clearly state that this tool searches for users. The name 'buscar_usuarios' implies searching, but the description should confirm the action and resource.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives (e.g., other search or list tools). The description only gives internal behavior (pagination, filtering by cargo) but does not specify contexts, prerequisites, or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JoseAlmeida-Ploomes/ploomes-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server