Skip to main content
Glama
uth-mail-mcp

uth-mail-mcp

by fotispetrou

whoami

Read-only

Verify mailbox login and identify the active account, mail servers, and quota in use before accessing the University of Thessaly email.

Instructions

Check that the login works and see which account, servers and mailbox quota are in use.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 and the description cannot contradict it. Beyond that, the description contributes that the call reports identity, server configuration and quota, but says nothing about failure behavior when login is invalid, which is the key behavioral question for a credential-checking 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 sentence, front-loaded with the primary purpose and carrying the return content in the same clause. Nothing is padded and no sentence is wasted.

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?

With no output schema, the description must carry the return-value burden, and it lists the three categories of information returned. It is not exhaustive about format or error signaling, but for a no-argument read-only tool that is a minor gap.

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?

There are no parameters, so the baseline of 4 applies and the description has no parameter semantics to add. It does not misrepresent any input.

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 concrete verb-plus-outcome ('check that the login works') and enumerates what is revealed: account, servers, and mailbox quota. That distinguishes it from every listed sibling, which are message and folder operations, though 'servers' stays slightly vague as to what server data is returned.

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

Usage Guidelines4/5

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

It establishes a clear use context — validating credentials and discovering the current identity/quota — which is the natural precursor to the search/send/move siblings. It stops short of stating when not to call it or naming an alternative, but for a zero-parameter diagnostic there is little competing choice to route away from.

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