Skip to main content
Glama
Sign In

Pineprompt

by com.pineprompt
OverviewDiscussionsAdmin

Update User Tool

update-user-tool
DestructiveIdempotent

Overwrites the given fields; previous values are not kept. Change a user's role within an organization. Allowed roles are admin and member; the organization owner's role cannot be changed and users cannot be promoted to owner.

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": {
      "organization_id": "<organization_id>",
      "user_id": "<user_id>",
      "role": "<role>"
    },
    "name": "update-user-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesThe new role for the user. Allowed values: admin, member. Promoting to owner is not supported.
user_idYesThe numeric id of the user whose role should be changed.
organization_idYesThe numeric id of the organization the user is a member of.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already indicate destructiveHint=true and idempotentHint=true, but the description adds specific context: previous values are not kept, and certain role changes are rejected. It does not state required permissions or what error occurs on an invalid role, but the destructive and scope behavior is well disclosed.

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?

The description is three short clauses with the most important warning first: previous values are not kept. It is easy to scan, but the role-enum restatement in the second and third sentences overlaps with the schema and could be trimmed.

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 small role-update tool with three fully documented parameters, the description covers the key constraints: destructive overwrite and owner-role immutability. With no output schema, it does not need to explain return values, but it could mention whether the previous role is ever needed or how the organization owner is identified.

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 100%, so the schema already documents all three parameters, including the role enum. The description restates the allowed roles and adds the owner-related constraint, which partially duplicates the schema's own role description. It adds little semantic meaning beyond the schema.

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?

The description states a specific verb and resource: change a user's role within an organization. It distinguishes this tool from delete-user-tool or update-brand-tool by naming the resource, although it doesn't explicitly contrast with sibling tools. Even so, its purpose is clear from the text alone.

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?

The description clearly implies when to use the tool: to change a user's role. It also defines usage limits, namely that the owner's role cannot be changed and that no promotion to owner is allowed. However, it never states when to use a different tool, such as delete-user-tool, or whether the user's organization membership must already exist.

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

All Pineprompt 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