Skip to main content
Glama

graph_create_master_category

Create a master category to organize mail and events by display name and color preset, optionally in a shared mailbox.

Instructions

Create a master category so it can be applied to mail and events.

The displayName is immutable after creation: to rename a category, delete it and create a new one. Colors are the presets preset0 through preset24.

Args: display_name: Name of the new category. color: Color preset, preset0 through preset24 (default "preset0"). mailbox: Shared mailbox address or user ID to act on. Empty targets your own mailbox. Requires the delegated Mail.*.Shared permissions.

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": {
      "display_name": "<display_name>"
    },
    "name": "graph_create_master_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNopreset0
mailboxNo
display_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does supply real behavior: displayName is immutable after creation, colors are constrained to preset0–preset24, and the shared-mailbox path requires delegated Mail.*.Shared permissions. It omits other important traits such as what happens on a duplicate name, whether the call is idempotent, and what is returned.

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 the action and the immutability caveat, then a compact Args block. Slight redundancy between the lead sentence and the Args entries, but nothing is wasted or buried.

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 three-parameter mutation tool with no annotations and no output schema, the definition covers purpose, the key behavioral constraint, and every parameter with defaults and permissions. The main residual gap is error and return behavior, which the agent would have to discover at call time.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does: it documents all three parameters, gives the default for color, spells out the valid range as preset0 through preset24, and explains that an empty mailbox targets the caller's own mailbox and which permissions shared targeting needs.

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?

States a specific verb and resource ('Create a master category') plus the downstream purpose ('so it can be applied to mail and events'), which an agent can act on directly. It does not explicitly distinguish itself from the sibling listing tool, but a create verb against a master category is unambiguous enough.

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?

Usage is implied by the purpose clause (create first, then apply to mail and events), and the rename guidance tells the agent that editing is not an option. There is no explicit statement of when not to use it or what to do instead, e.g. whether to check for an existing category first via the list tool.

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

Deploy Server

Other Tools