Skip to main content
Glama
Sign In

Busymail

by app.busymail
OverviewDiscussionsAdmin

Pin a cluster

pin_cluster

Pin a whole cluster to the user's Pins tab. Affects Busymail only: nothing moves in the mailbox. The reply's result field says pinned, no_such_cluster when the key and category match none of the user's conversations, or pinned_but_nothing_in_feed - the pin is made, but the feed does not render this cluster, because everything in it is archived, not yet extracted, or written only by the user, so nothing will show the pin until that changes. Any individual thread-pins inside the cluster are DELETED, since the cluster pin covers those threads - removing the cluster pin later does not bring them back, so do not use this to pin a cluster temporarily. Takes a cluster_key and category exactly as list_feed reported them. Pinning something already pinned is not an error.

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": {
      "cluster_key": "<cluster_key>",
      "category": "<category>"
    },
    "name": "pin_cluster"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYesThe category list_feed reported for this cluster.
cluster_keyYesThe cluster key from list_feed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the behavioral burden very well. It discloses that the mailbox is unaffected, that existing individual thread-pins are permanently deleted, that repeated pinning is idempotent rather than an error, and the possible result values including the important pinned_but_nothing_in_feed case.

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?

The purpose and scope are front-loaded, and each sentence contributes operationally useful information. However, the dense single paragraph and especially the long explanation of pinned_but_nothing_in_feed make it somewhat harder to scan.

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?

The definition covers scope, parameter provenance, destructive side effects, idempotency, and result statuses, which is particularly valuable because there is no output schema. It provides the information an agent needs to select and invoke the tool safely.

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 description coverage is 100%, and both parameters already state that their values come from list_feed. The description's instruction to pass them exactly as reported reinforces correct usage but adds little parameter meaning beyond the schema.

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 clearly states the verb, resource, and destination: pinning a whole cluster to the user's Pins tab. "Whole cluster" and the discussion of individual thread-pins also distinguish it from the sibling pin_conversation tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete invocation guidance by requiring cluster_key and category exactly as list_feed reported them. It also supplies an explicit when-not warning: do not use this for temporary cluster pins because prior individual thread-pins will not be restored.

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

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