Skip to main content
Glama
Quolle MCP

Quolle MCP

by Quolle-main

Get email status

get_email
Read-only

Retrieve an email by ID to check delivery status (queued, sent, delivered, bounced, failed) and open/click metrics.

Instructions

Look up one email by id: status (queued, sent, delivered, bounced, complained, failed…) and open/click counts.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe email id returned by send_email.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / id / description
      Previous value: -"The email ID returned by send_email."New value: +"The email id returned by send_email."
  2. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover readOnly and closed-world, and the description adds genuinely new context by enumerating the status vocabulary (queued, sent, delivered, bounced, complained, failed) and the engagement counters returned. It doesn't mention behavior for unknown ids or whether counts lag, which keeps it short of a 5.

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?

A single sentence, front-loaded with the verb and resource, with the return fields appended compactly. No 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, listing the returned status values and counters is exactly the right compensation, and a single required id keeps the call simple. Minor gap: nothing about failure/not-found behavior.

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 coverage is 100% and the id property already says 'returned by send_email'; the description's 'by id' adds no format or semantics beyond that. Baseline 3 applies since the schema does the heavy lifting.

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 ('Look up one email by id') plus the data returned (status enum examples, open/click counts). The singularity 'one email' implicitly contrasts with list_emails, but no sibling is named explicitly.

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?

Usage is only implied: 'by id' plus the schema note that the id comes from send_email suggests calling this after sending, and 'one email' hints that list_emails is the bulk alternative. No explicit when-to-use or when-to-prefer-a-sibling statement.

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