Skip to main content
Glama

list_inbox

Retrieves accounts-payable inbox emails in chronological order, optionally filtered to messages received on or after a specified day, so AI agents can review invoices and vendor correspondence.

Instructions

Emails received so far in the AP mailbox, oldest first.

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_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
since_dayNoOnly emails received on or after this day.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure, and it does contribute the sort order (oldest first) and mailbox scope. It says nothing about pagination, result limits, or whether full bodies or just headers/summaries are returned, which matters for a listing tool paired with a read 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?

A single short sentence, front-loaded with the resource and scope, with zero filler or repetition of the tool name.

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 one-parameter read tool this covers the essentials, but with no output schema the agent has no way to know the shape of returned email records (IDs, fields, truncation), and no volume/pagination expectations are set.

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?

There is a single optional parameter and the schema documents it fully ('Only emails received on or after this day'), so the schema does the heavy lifting. The description adds no additional meaning about how since_day interacts with the oldest-first ordering.

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 names a specific verb and resource (emails received in the AP mailbox) plus the ordering (oldest first), which clearly separates it from a single-message reader like read_email. It stops short of explicitly contrasting with any sibling, but the listing scope is unambiguous.

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 implied by the phrasing 'emails received so far in the AP mailbox' – an agent can infer this is the entry point for browsing the inbox rather than reading one message. There is no explicit when-to-use, when-not-to-use, or named alternative such as read_email.

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