Skip to main content
Glama

Get SharePoint Site

get_site
Read-only

Retrieve SharePoint site details by site ID to inspect site metadata and properties before accessing lists, libraries, or other site content.

Instructions

Get SharePoint site details

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": {
      "site_id": "<site_id>"
    },
    "name": "get_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYesSite ID (e.g., 'contoso.sharepoint.com,siteId,webId')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

The readOnlyHint annotation already declares this is a safe read, so the description's job is to add context beyond that — and it adds none. It does not say what fields are returned, whether the composite site_id format is required, or what happens on an invalid or inaccessible site; the only hint about ID format lives in the schema, not the description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no filler and the operation front-loaded. It is efficient, though its brevity reflects under-specification rather than disciplined editing.

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 one-parameter read tool with full schema coverage, readOnly annotations, and no output schema, a minimal description is nearly sufficient. Still, one sentence naming the returned fields would materially help an agent decide between this and the site-listing siblings.

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

Parameters3/5

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

Schema coverage is 100% and the single site_id parameter is fully documented in the schema with the composite 'contoso.sharepoint.com,siteId,webId' example. The description adds nothing beyond that, so the baseline 3 applies.

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

Purpose3/5

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

"Get SharePoint site details" states a verb (get) and a resource (SharePoint site), so the basic operation is identifiable. However, "details" is vague about what is returned, and the description offers no differentiation from siblings such as list_site_drives or get_drive_item, which also operate on site-scoped data.

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 use this tool versus alternatives like list_site_drives or search_site_files, and no prerequisites or exclusions are stated. The agent must infer that this is the entry point for resolving a site_id into site metadata.

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