TalaLevel

One email in full

get_email

Read-onlyIdempotent

One email whole, by its id from list_lead_emails or search_emails (gmail:…, campaign:…, or an older imported id): sender, recipients, subject, file names and the full words. Read it before quoting or answering a message the list only showed the start of.

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": {
      "email_id": "<email_id>"
    },
    "name": "get_email"
  }
}

Input Schema

Name	Required	Description	Default
`email_id`	Yes	The email's id, e.g. gmail:123.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive retrieval. The description adds useful behavioral detail about what is returned: sender, recipients, subject, file names, and full message text.

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 description is compact and front-loads the tool's purpose. The parenthetical ID formats are dense but purposeful, and the second sentence clearly explains when to read the full message.

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?

For a simple one-parameter read tool with complete annotations and high schema coverage, the definition provides enough context to select and call it correctly. It covers purpose, ID sources, and returned content without unnecessary detail.

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%, so the schema already documents the single email_id parameter. The description adds useful meaning beyond the schema example by listing accepted ID forms such as gmail:, campaign:, and older imported IDs.

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 states a specific retrieval operation: one complete email by ID. It explicitly distinguishes this from list/search tools by noting the ID comes from list_lead_emails or search_emails and that this tool returns the full content.

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?

It gives clear context for when to use the tool: before quoting or answering a message that a list only partially showed. It also names where IDs come from, though it does not explicitly state when not to use it versus list/search.

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

All TalaLevel tools Inspect

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

Need Help?