Skip to main content
Glama

Grant MCP tool

grant_mcp_tool
Destructive

Grant one of a registered MCP server's tools to an organisation role, making it callable from agent runs. Organisation admins only. Registration alone offers nothing: each tool needs a grant, and the server's permission tier still gates writes (a write-classified tool never runs under the read_only tier). Grant the adapter's recommended_tools first (get_mcp_catalog) rather than blanket-granting an unknown inventory.

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": {
      "server": "<server>",
      "tool_name": "<tool_name>"
    },
    "name": "grant_mcp_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverYesThe registered server's name or id (see list_mcp_servers).
tool_nameYesThe remote tool name to grant (max 160 chars), e.g. 'list_incidents'.
allowed_to_roleNoThe organisation role granted access (default 'member').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, and the description adds real context beyond them: the admin-only authorization requirement and the fact that the server's permission tier still gates writes, so a write-classified tool never runs under read_only. It does not explain reversibility or what a repeat grant of the same tool does, which is the remaining behavioral gap.

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?

Three dense sentences with the core action and effect front-loaded, followed by authorization, prerequisite ordering, and the tier caveat. No sentence restates a structured field or wastes words.

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 3-parameter mutation with no output schema, it covers the pieces an agent needs: who may call it, that registration must precede it, how the permission tier interacts with it, and which tools to grant first. Only the response shape and the effect of re-granting are left unstated.

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; the description earns above that by tying tool_name selection to the catalog's recommended_tools and by framing allowed_to_role as the organisation role receiving access. Exact referral syntax and char limits stay in the schema, which is appropriate.

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?

It states a specific verb and resource - 'Grant one of a registered MCP server's tools to an organisation role' - and adds the effect ('making it callable from agent runs'), which distinguishes it from register_mcp_server and get_mcp_catalog without opening either schema.

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 explicit prerequisites ('Registration alone offers nothing: each tool needs a grant') and a sequencing recommendation to grant the adapter's recommended_tools from get_mcp_catalog before blanket-granting, which functions as a when-not caution. It does not name a distinct alternative tool for a different grant scenario, so it falls just short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.