Skip to main content
Glama
Sign In
Microsoft Fabric MCP Server

Microsoft Fabric MCP Server

by Jasuni69
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

graph_mail

Send email messages on behalf of the current identity via Microsoft Graph. Specify recipients, subject, and body to deliver mail directly.

Instructions

Send mail via Microsoft Graph on behalf of the current identity.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "to": "<to>",
      "subject": "<subject>",
      "body": "<body>"
    },
    "name": "graph_mail"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
bodyYes
subjectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'on behalf of the current identity,' which hints at auth context, but it does not disclose side effects, permissions needed, whether sending is irreversible, or what happens on failure. For a side-effecting email-sending action, this is a significant gap.

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 that front-loads the verb and entity, includes a useful identity qualifier, and contains no filler. It earns every word.

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 simple three-string-parameter tool with no output schema, the description is minimally viable: it tells the agent what action to take and under whose identity. However, with no annotations and no return-value information, it leaves behavioral and edge-case details unspecified.

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 it adds no parameter-level detail. The parameter names 'to', 'subject', and 'body' are self-evident in an email context, but the description does not clarify formats, recipient syntax, or body type.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('Send mail') and resource ('via Microsoft Graph'), and clarifies the acting identity ('current identity'). This clearly distinguishes it from sibling graph_teams_message, which sends Teams messages instead of email.

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?

The description gives clear context: use this tool to send email as the current user via Microsoft Graph. It does not explicitly name alternatives or say when not to use it, but the 'mail' vs. 'teams_message' distinction is apparent enough that an agent can select appropriately.

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

Deploy Server

Other Tools