Skip to main content
Glama
Sign In
allinbox

allinbox

by tomasbenavidez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

search_all

Read-only

Search all connected email accounts in one call and return one line per message (ID, date, sender, subject), merging duplicates across accounts. Leave the query empty to list recent messages.

Instructions

Search ALL email accounts in one call. Returns one line per message: id | date | from | subject. Duplicates across accounts (same Message-ID) are merged. Empty query = latest messages.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_all"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoFree text: words, sender name or address, subject.
accountsNoRestrict to these account ids. Default: all.
since_daysNoOnly messages newer than N days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's job is to add context, which it does: it discloses the exact return line format (id | date | from | subject) and the cross-account deduplication by Message-ID. Neither of those behaviors is inferable from the schema or annotations.

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 short sentences, front-loaded with the scope, then the return shape, then the dedup and empty-query behaviors. No sentence restates the name or title and none is filler.

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 takes on the burden of describing results and does so concretely. The gaps are minor: it doesn't say whether body text is searched or how `limit` interacts with the merged result set.

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 75%, so most parameters are already documented. The description adds meaning beyond the schema by explaining the empty-query behavior for the `query` parameter and reinforcing that the default scope spans all accounts (which the `accounts` schema also notes).

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?

The description opens with a specific verb and resource ('Search ALL email accounts') and clarifies the scope with 'in one call'. It is clearly distinguishable from read_email/read_thread in practice, though it never names those siblings explicitly to force the distinction.

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?

It offers one useful usage cue — 'Empty query = latest messages' — which tells the agent how to browse rather than search. However, there is no explicit statement of when to prefer this over read_email or read_thread, or when to pass a query versus leaving it empty for recent mail.

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