Skip to main content
Glama

maily_search

Search email across all accounts by subject, body, or sender, or restrict results to a single profile. Returns matching messages with an optional result limit.

Instructions

Local full-text search (subject, body, sender). Optional profile to restrict it to one account; otherwise searches every profile.

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": {
      "query": "<query>"
    },
    "name": "maily_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
profileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

B3.3/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses that the default scope is every profile, which is meaningful cross-account behavior, but says nothing about result ordering/ranking, whether only locally synced mail is indexed, or how limit truncation behaves.

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 tight sentences, front-loaded with the core behavior and followed by the scoping caveat. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter search tool with no annotations and no output schema, the essentials are present but key details are missing: how profiles are identified, what the results look like, and whether a prior maily_sync is required for local search to return anything.

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 0%, so the description must compensate. It explains the `profile` parameter well (restrict to one account vs. search all) and clarifies what `query` matches against, but `limit` is never mentioned and the format of a profile identifier (name, email, id) is left ambiguous.

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 ('full-text search') and narrows scope to subject, body, and sender, which distinguishes it from maily_list_messages. It never names the sibling it differs from, so an agent must infer the search-vs-list boundary.

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

Usage Guidelines2/5

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

The description explains the profile scoping option but gives no guidance on when to search versus when to use maily_list_messages or maily_get_message, and no prerequisites (e.g., whether messages must be synced first). Usage is only implied by the word 'search'.

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