Skip to main content
Glama

reply_all_email

Send responses to all recipients in an email thread using the Microsoft MCP server, simplifying group communication through structured inputs for account, email ID, and message body.

Instructions

Reply to all recipients of an email

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYes
bodyYes
email_idYes

Implementation Reference

  • Implementation of the reply_all_email tool. Uses Microsoft Graph API to POST to /me/messages/{email_id}/replyAll with the provided body text. Registered via @mcp.tool decorator.
    @mcp.tool
    def reply_all_email(account_id: str, email_id: str, body: str) -> dict[str, str]:
        """Reply to all recipients of an email"""
        endpoint = f"/me/messages/{email_id}/replyAll"
        payload = {"message": {"body": {"contentType": "Text", "content": body}}}
        graph.request("POST", endpoint, account_id, json=payload)
        return {"status": "sent"}
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('reply') but doesn't mention permissions required, whether it's a mutation (likely yes), rate limits, or what the response looks like. This leaves significant gaps for a tool that modifies data.

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?

The description is a single, efficient sentence with zero wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly without unnecessary elaboration.

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?

Given the complexity of an email reply tool with 3 parameters, no annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects, parameter meanings, or output expectations, making it inadequate for safe and effective use by an agent.

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 for undocumented parameters. It adds no meaning beyond the schema, failing to explain what 'account_id', 'email_id', or 'body' represent or how they should be formatted, leaving all three parameters semantically unclear.

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') and target ('to all recipients of an email'), which is specific and unambiguous. However, it doesn't explicitly differentiate from its sibling 'reply_to_email' (which presumably replies to the sender only), missing full sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives like 'reply_to_email' or 'send_email'. It lacks context about prerequisites (e.g., needing an existing email) or exclusions, offering minimal usage direction.

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