Skip to main content
Glama
Sign In

Mailbuttons

by com.mailbuttons
OverviewDiscussionsAdmin

Request capability / environment promotion

mailbuttons_request_promotion

File a human-approval request to grant additional capabilities (e.g. send_external) or promote a sandbox token to production. The token CANNOT widen its own scope; this only opens a request and returns an approval URL.

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": {
      "grant_capabilities": "<grant_capabilities>"
    },
    "name": "mailbuttons_request_promotion"
  }
}

Input Schema

NameRequiredDescriptionDefault
inbox_idNoOptional inbox to scope the requested grant to.
promote_toNoRequest promotion of a sandbox token to production.
grant_capabilitiesYesCapabilities to request, e.g. send_external, attachments. A token can never widen its own scope — this only files a request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already disclose write semantics (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), and the description adds genuinely useful context beyond them: the call does not mutate permissions itself, it only opens a request and returns an approval URL, requiring human approval. It stops short of covering duplicate-request or expiry behavior.

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?

Two tightly written sentences, with the primary purpose front-loaded and the critical constraint (no self-scope-widening, request-only) placed immediately after. No filler or redundant restatement of the name.

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?

With no output schema, the description usefully states the return value (an approval URL) and the human-approval nature of the flow. It leaves some gaps around what happens after approval, request expiry, or duplicate submissions, but covers what an agent needs to invoke it 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 each parameter is already documented, so the schema does the heavy lifting. The description echoes the capability example (send_external) and the sandbox-to-production promotion but adds no format or syntax detail beyond the schema, matching the baseline for full coverage.

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?

The description states a specific verb and resource ('File a human-approval request') plus the two distinct purposes it serves: granting capabilities and promoting a sandbox token to production. It also draws a clear boundary ('The token CANNOT widen its own scope'), which no sibling tool shares, so an agent can distinguish it immediately.

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 clear triggering context (need additional capabilities like send_external, or sandbox-to-production promotion) and clarifies that the call only files a request rather than effecting the change. It does not explicitly state when not to use it or name alternatives, but no sibling tool competes for this job.

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

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