Skip to main content
Glama

update-role

Update a role's name, permissions, level, and other attributes. Modify role details to reflect organizational changes.

Instructions

Update an existing role with new information or permissions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoRole name
levelNoRole level/hierarchy
activeNoActive status (1=active, 0=archived)
role_idYesThe role ID (role_id)
descriptionNoRole description
permissionsNoList of permissions for this role
department_idNoDepartment ID if role is department-specific
is_system_roleNoWhether this is a system role (1=system, 0=custom)
default_hourly_rateNoDefault hourly rate for this role
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It only says 'update', implying mutation, but fails to mention whether updates are partial or full replacements, effect on permissions, idempotency, or required authorization.

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

Conciseness3/5

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

The description is a single sentence, making it concise, but it lacks important details that could be added without excessive verbosity.

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 9 parameters, no output schema, and no annotations, the description is too sparse. It does not explain behavior like partial updates, permission overwriting, or return values, making it incomplete for effective tool use.

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 coverage is 100%, so the schema already describes all parameters. The description adds no extra meaning beyond the schema, so a baseline score of 3 is appropriate.

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 clearly states 'Update an existing role with new information or permissions', which is a specific verb-resource combination. However, it does not differentiate from the sibling tool 'update-role-permissions', which may cause confusion.

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 like 'update-role-permissions' or 'create-role'. The absence of context leaves the agent without decision criteria.

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/asachs01/float-mcp'

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