Skip to main content
Glama
uth-mail-mcp

uth-mail-mcp

by fotispetrou

list_folders

Read-only

List all mail folders with message and unread counts, including role labels for inbox, sent, drafts, trash, junk, and archive, to help you locate and manage mailbox content.

Instructions

All mail folders with their message and unread counts. role marks the inbox, sent, drafts, trash, junk and archive folders.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered without the description. The description adds a small but real behavior detail — that each folder carries message and unread counts and a 'role' marker for inbox/sent/drafts/trash/junk/archive — which helps an agent interpret results, but says nothing about ordering, limits, or what happens with nested folders.

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 short sentences, front-loaded with the resource and its payload, and the second sentence earns its place by explaining the 'role' field the caller will see. No filler or restatement of the tool name.

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-parameter read tool with an output schema and read-only annotations, this is close to sufficient. The only mild gap is that it does not state whether the list is complete versus paginated, though 'All mail folders' implies completeness.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond what the schema shows. Baseline of 4 applies for a parameterless tool.

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 the resource ('All mail folders') and what accompanies it ('message and unread counts'), so the agent knows this is a folder-listing/retrieval operation rather than a message or attachment operation. It does not explicitly contrast with siblings such as search_messages, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives for discovering mail structure. The agent must infer from the tool name and sibling list that this is the entry point for folder discovery.

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