Radar noEixo

Update team member

update_team_member

DestructiveIdempotent

Muda o cargo de um membro ou gera uma senha temporária nova para ele. Dono e gerente podem usar, mas o gerente só age sobre quem está abaixo dele (operador, especialista, técnico) e só atribui cargo abaixo do seu. Ninguém altera a própria conta por aqui. Permissões recurso a recurso ficam em update_team_member_permissions.

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

Input Schema

Name	Required	Description
`role`	No	Cargo novo.
`member_id`	Yes	ID do membro (de list_team_permissions).
`reset_password`	No	true gera uma senha temporária nova; ela volta UMA vez nesta resposta.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, but the description adds the authorization/hierarchy model that the annotations cannot express, which is the highest-value behavioral context here. It does not discuss irreversibility of a role change or what happens to a member's other state, which the destructive flag implies.

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?

Four short sentences, capability first and constraints after, with zero filler. Every clause carries either a permission rule or a routing instruction.

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 three-parameter mutation with rich annotations and no output schema, the description covers who may call it, scope limits and the sibling boundary. It would be complete with a note on what failure looks like when a manager targets a peer or superior, but nothing essential is missing.

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 semantics the schema cannot: which roles a manager is allowed to assign relative to their own. The temporary-password behavior is left to the schema's reset_password description rather than repeated.

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?

States two specific operations on a specific resource (change role, generate temporary password) and explicitly routes permission-editing elsewhere. The contrast with update_team_member_permissions makes selection unambiguous despite a large sibling list.

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

Usage Guidelines5/5

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

Gives explicit preconditions: owner and manager may use it, manager is limited to subordinates (operator, specialist, technician) and to assigning roles below their own. It also names an exclusion ('ninguém altera a própria conta por aqui') and the alternative tool for permissions.

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

All Radar noEixo tools Inspect

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

Need Help?