Skip to main content
Glama
yahoo-mail

yahoo-mail

by soothslayer

doctor

Read-onlyIdempotent

Verify Yahoo Mail IMAP and SMTP login credentials without sending an email, confirming account access works before configuring mail clients or automation.

Instructions

Verify Yahoo IMAP and SMTP login without sending an email.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish that this is a safe, idempotent, read-only, network-touching call. The description's one added behavioral fact is that no email is dispatched, which is genuinely useful and not in the annotations. It stops short of covering auth requirements, failure behavior, or what a failed check reports.

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 action front-loaded and the key caveat (no email sent) attached directly to it. No filler, no repetition of the 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 no-argument, read-only diagnostic this is close to sufficient, and annotations cover the safety profile. With no output schema, though, the description leaves the agent guessing what a verification result looks like and how failures surface, which matters for a diagnostic tool.

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 the baseline is 4; there are no inputs whose meaning could be clarified further. Nothing in the description is needed to explain arguments.

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?

"Verify Yahoo IMAP and SMTP login" gives a specific verb plus the exact resources being checked, and the trailing clause rules out the obvious confusion with a mail-sending tool. It is clear without naming a sibling, so it falls just short of the top mark.

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?

The phrase "without sending an email" implies a credential/connectivity health check rather than normal mail work, which is useful implied guidance. However, it never states when an agent should call this instead of something like send_status, nor any prerequisite such as configured credentials.

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