Skip to main content
Glama
Sign In
Microsoft Graph MCP Server

Microsoft Graph MCP Server

by ry-ops
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_root_site

Retrieve the root SharePoint site for a tenant to identify the top-level site and support SharePoint administration or content access.

Instructions

Get the root SharePoint site for the tenant

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/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, and it adds essentially none. It doesn't state that the call is read-only, what permissions are required, whether it fails when no root site exists, or whether the response is a site object or a URL. Only the implicit 'Get' conveys non-destructiveness.

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 nine-word sentence with no filler, and the identifying qualifier ('root SharePoint site') is front-loaded. Nothing is wasted or buried.

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 zero-param lookup with no output schema, the description should say what comes back (a site resource? a URL? a site ID to feed into get_site_by_url). It establishes the target but stops short of making the return value usable for chaining into the site tools.

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 takes zero parameters and the schema is empty, so there is nothing to document; baseline 4 applies. The description correctly implies no input is needed by scoping the site to the tenant implicitly.

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 and resource ('Get the root SharePoint site') plus a scope qualifier ('for the tenant') that separates it from get_site, get_site_by_url and list_sites. It never names those siblings explicitly, but the word 'root' does the disambiguating work.

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?

There is no guidance on when to call this versus get_site, get_site_by_url or list_sites, and no stated prerequisites or exclusions. The agent must infer from the word 'root' alone that this is the entry-point site rather than an arbitrary one.

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