Skip to main content
Glama

roles_delete_role_setting

Delete a role setting to remove custom permissions. Reverts to default value if available. Requires admin permissions.

Instructions

Delete a role setting.

Removes a setting from a role. Requires admin permissions.

Workflow tips:

  • Reverts to default value if available

  • Use roles/get_role_settings to see current settings

  • Changes affect all users with this role

Common use cases:

  • Remove setting: { "id": 123, "setting_key": "custom_permission" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the role
setting_keyYesKey of the setting to delete
Behavior4/5

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

No annotations provided; description covers effect (reverts to default value), impact (affects all users with role), and permission requirement. Missing details on idempotency or error handling but adequate.

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?

Front-loaded with main action, then organized into details. Some repetition (e.g., 'Removes a setting from a role' redundant with title) but overall efficient.

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?

Covers purpose, permissions, behavior, and provides example. References companion tool get_role_settings. Adequate for agent to select and invoke correctly.

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%, and description does not add new semantic meaning beyond schema. The example usage confirms parameter usage but does not explain parameter constraints or behavior.

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?

Clearly states 'Delete a role setting', specifies the resource and action. Distinguishes from sibling tools like roles_add_role_setting and roles_update_role_setting.

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?

Provides workflow tips and common use cases, mentions admin permission requirement, suggests checking current settings with get_role_settings. Could explicitly compare with update tool but still helpful.

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/iamsamuelfraga/mcp-pipedrive'

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