Skip to main content
Glama
Sign In

Radar noEixo

by com.noeixodigital
OverviewDiscussionsAdmin

Update team member permissions

update_team_member_permissions
DestructiveIdempotent

Altera o que um membro da equipe pode fazer, recurso a recurso. Passe em "permissions" só os recursos que quer mudar — o resto segue o padrão do cargo. Para devolver alguém inteiramente ao padrão do cargo, passe reset: true. Só quem administra a conta pode usar, e ninguém altera as próprias permissões. IMPORTANTE: a mudança passa a valer no PRÓXIMO LOGIN da pessoa (a sessão atual dura até 7 dias).

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": {
      "member_id": "<member_id>"
    },
    "name": "update_team_member_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
resetNotrue devolve o membro ao padrão do cargo e ignora "permissions".
member_idYesID do membro (de list_team_permissions).
permissionsNoMapa recurso -> nível, ex: {"automacoes":"write","integracoes":"none"}. Níveis: none | read | write. Chave ou nível desconhecido é ignorado.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, it discloses critical behavior: changes take effect only on the member's next login, current sessions last up to 7 days, only admins can call it, and no one can change their own permissions. These are material operational details that an agent needs before invoking a destructive permission-change tool.

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?

The description is front-loaded with purpose, then proceeds directly to partial-update behavior, reset behavior, authorization constraints, and the login-timing caveat. Every sentence adds operational value with no wasted text.

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

Completeness5/5

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

For a destructive, admin-only permission mutation with no output schema, the description covers the key concerns: partial updates, reset semantics, authorization, and delayed effect. The annotations and full schema coverage handle the remaining structured details.

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 100%, so the baseline is 3, but the description adds useful semantics: permissions is a partial map, unspecified resources fall back to the role default, and reset: true overrides permissions entirely. These details go beyond the schema's field-level descriptions.

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

Purpose5/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: it changes what a team member can do, resource by resource. This clearly distinguishes it from sibling tools like update_team_member, which handles member data rather than permissions.

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

Usage Guidelines4/5

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

It gives clear operational guidance: pass only the resources to change, use reset: true to return to role defaults, and only account admins can use it. It does not explicitly name sibling alternatives, but the usage context is strong and the exclusions are clear.

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

All Radar noEixo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources