Skip to main content
Glama
yahoo-mail

yahoo-mail

by soothslayer

list_folders

Read-onlyIdempotent

List selectable Yahoo Mail folders and their special-use flags so you can choose the correct mailbox location for reading, searching, or sending messages.

Instructions

List selectable Yahoo mail folders and their special-use flags.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by revealing that only 'selectable' folders are returned and that special-use flags are surfaced. It says nothing about authentication requirements or whether results vary per account.

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 with the scope restriction front-loaded and no filler. Every word ('selectable', 'special-use flags') carries information.

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-only list tool with annotations covering the safety profile, the description is close to complete; it names the resource and the distinguishing returned attribute. It stops short of describing the entry shape (name vs. id vs. flags format) needed to use the output, which matters more here because no output schema exists.

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 no parameter meaning to compensate for; baseline 4 applies. The description correctly signals a no-argument, whole-account listing.

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 ('List ... Yahoo mail folders') plus a meaningful scope qualifier ('selectable') and the notable attribute returned ('special-use flags'). It does not name a sibling to contrast with, but the operation is unambiguous against siblings like read_message or search_messages.

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: an agent can infer this is the discovery step before picking a folder. There is no explicit 'use this when...' statement, no exclusion of alternatives, and no note about whether folder IDs returned here are the ones accepted elsewhere.

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