Skip to main content
Glama
Sign In
Enterprise Microsoft 365 MCP Server

Enterprise Microsoft 365 MCP Server

by ManoAlee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

m365_list_tenant_allow_list

Lists entries in the Microsoft Defender Tenant Allow/Block List, including senders, domains, and URLs, to help admins review tenant-wide allow and block configurations.

Instructions

Lists entries in the Microsoft Defender Tenant Allow/Block List (senders, domains, URLs).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/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 behavioral burden. 'Lists' implies read-only, but the description does not disclose auth requirements, rate limits, pagination, or whether both allow and block entries are returned; it only names the entry categories.

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 front-loaded sentence with no filler. It names the verb, resource, and entry types efficiently, with every phrase earning its place.

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?

For a no-parameter list tool with an output schema, the description identifies the resource and entry categories sufficiently. A brief read-only or auth note would have improved safety clarity in the absence of annotations, but it is otherwise adequate.

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 has zero parameters, so the baseline is 4. The description appropriately adds no parameter semantics because none exist, and the empty schema leaves nothing further to explain.

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?

States a specific verb ('Lists') and exact resource ('Microsoft Defender Tenant Allow/Block List'), with a parenthetical naming entry types. It implicitly distinguishes itself from m365_add_sender_to_allow_list by verb, but does not explicitly name alternatives or siblings.

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 gives no when-to-use, when-not-to-use, prerequisites, or alternative routing. It implies inspection of the allow/block list, but leaves all usage context to inference.

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