Skip to main content
Glama
Vaartix MCP server

Vaartix MCP server

Official
by vaartix-mail

List emails

list_emails
Read-only

Retrieve recent emails newest first with optional filters for date range, status, and search to review message activity or locate specific sends.

Instructions

List recent emails, newest first, with optional filters. Needs read access: a full-access API key, or the read permission when signed in.

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": "list_emails"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoOnly emails from the last N days
limitNo1 to 100, default 20
beforeNoReturn emails older than this email ID (paging)
searchNoSearch recipient, sender or subject
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description adds the genuinely useful auth requirement (full-access API key or read permission) and the newest-first ordering. It stops short of any rate-limit, truncation, or paging behavior beyond what the schema implies.

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?

Two short sentences with the core purpose first and the access constraint second; every clause carries information and there is no filler. It could be marginally tighter by folding the auth note into a single clause, but the structure is sound.

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 zero-required-parameter read tool with annotations present and no output schema, the definition covers purpose, ordering, filtering and authorization. The remaining gaps — paging behavior with 'before' and result-set truncation — are partly covered by schema descriptions, so nothing critical is missing.

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 80%, so the schema already documents days, limit, before, search and status boundaries and enum values. The phrase 'optional filters' only confirms all are optional, adding no semantics beyond the schema; baseline 3 applies.

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 gives a specific verb and resource ('List recent emails') plus ordering ('newest first') and scope ('optional filters'). An agent can distinguish it from get_email or cancel_email, though the description itself never names a sibling or explicit contrast.

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?

Usable context is implied by 'recent emails... with optional filters', which signals a filtered listing operation. There is no explicit when-to-use or when-not guidance, no statement about which alternative to pick for a single message versus a listing, and no mention of pagination strategy despite a paging param existing.

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