Skip to main content
Glama

reply_to_email

Automatically generate and send email replies using Microsoft Graph API. Specify account ID, email ID, and response body to streamline communication directly through your Outlook inbox.

Instructions

Reply to an email (sender only)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYes
bodyYes
email_idYes

Implementation Reference

  • The `reply_to_email` tool handler function. It sends a reply to the specified email using Microsoft Graph API. The @mcp.tool decorator also registers it as an MCP tool.
    @mcp.tool
    def reply_to_email(account_id: str, email_id: str, body: str) -> dict[str, str]:
        """Reply to an email (sender only)"""
        endpoint = f"/me/messages/{email_id}/reply"
        payload = {"message": {"body": {"contentType": "Text", "content": body}}}
        graph.request("POST", endpoint, account_id, json=payload)
        return {"status": "sent"}
  • The @mcp.tool decorator registers the reply_to_email function as an MCP tool.
    @mcp.tool
Behavior2/5

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

With no annotations, the description carries full burden but provides minimal behavioral insight. It implies a write operation ('reply') but doesn't disclose permissions, side effects (e.g., email sent immediately vs. saved as draft), rate limits, or response format. The 'sender only' adds some context but leaves critical gaps for a mutation 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?

Extremely concise with a single, front-loaded sentence that wastes no words. The phrase 'sender only' efficiently clarifies scope without redundancy, making it appropriately sized for the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Incomplete for a mutation tool with no annotations, no output schema, and 0% schema coverage. The description lacks details on behavior, parameters, and expected outcomes, leaving the agent with insufficient context to use it effectively beyond basic intent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate but adds no parameter details. It doesn't explain what 'account_id', 'email_id', or 'body' represent, their formats, or constraints (e.g., 'body' as HTML/text). This leaves all three parameters semantically unclear beyond schema titles.

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 clearly states the action ('reply to') and resource ('an email'), with the clarifying scope 'sender only' distinguishing it from 'reply_all_email'. However, it doesn't explicitly differentiate from 'send_email' or 'create_email_draft', which could be alternatives for email composition.

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?

No explicit guidance on when to use this tool versus alternatives like 'reply_all_email', 'send_email', or 'create_email_draft'. The 'sender only' hint implies a distinction from 'reply_all_email', but lacks context on prerequisites (e.g., needing an existing email) or exclusions.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/elyxlz/microsoft-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server