Skip to main content
Glama

Do two emails reach the same inbox?

same_inbox
Read-onlyIdempotent

Compares two addresses after normalising Gmail dots, +tags and googlemail.com. Use it to spot one person signing up again for a free trial with an alias (j.ane+2@gmail.com vs jane@gmail.com).

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": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "same_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesFirst email address
bYesSecond email address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description usefully adds the normalisation behaviour that determines the answer, but says nothing about the result shape or how non-Gmail domains are treated, which is a real behavioural gap for a comparison tool.

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 sentences: the first states what is compared and under which normalisation, the second gives the motivating use case with a concrete example. Nothing is redundant and the core behaviour is front-loaded.

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 two-parameter comparator with full schema coverage and annotations covering side effects, this is nearly complete. The only omission is edge-case behaviour for non-Gmail addresses or malformed input, which an agent might need before calling it on arbitrary domains.

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 100% and both parameters are already described as email addresses, so the baseline is 3. The description earns an extra point by explaining that inputs are normalised before comparison, which tells an agent how 'a' and 'b' are actually interpreted.

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?

States a specific verb (compares) and resource (two email addresses) plus the exact normalisation rules applied (Gmail dots, +tags, googlemail.com), which makes the tool's scope unambiguous and separates it from siblings like check_email.

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?

Gives a concrete triggering scenario — detecting a repeated free-trial signup via an alias, with a worked example pair. It stops short of stating when NOT to use it or naming an alternative tool for general address validation.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources