Skip to main content
Glama

List SharePoint Sites

list_sites
Read-only

Lists SharePoint sites: returns followed sites by default, or searches all sites when given a query.

Instructions

List SharePoint sites. Without a query, returns followed sites. With a query, searches all sites.

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

Input Schema

NameRequiredDescriptionDefault
queryNoSearch query to find sites (omit to list followed sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuinely useful non-obvious behavior: the no-argument default returns only followed sites, not all sites. It says nothing about result caps, pagination, or ordering, and there is no output schema to fill that gap.

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?

Two short sentences, front-loaded with the resource and then the conditional behavior; nothing is redundant. It is slightly terse for a tool with two distinct result sets, but no sentence is wasted.

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 one-optional-parameter, read-only list tool with full schema coverage and annotations, the description covers the essential decision an agent must make. Only secondary details like result limits or default ordering are absent.

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 description coverage is 100% and the single query parameter is already documented in the schema. The description reinforces the omit-vs-provide semantics but adds no format, syntax, or scoping detail beyond what the schema already states. Baseline 3 applies.

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 ('List SharePoint sites') and immediately explains two distinct modes, so an agent knows exactly what the call returns. It does not name or distinguish itself from any sibling such as list_site_drives or list_site_items, which keeps it just short of a 5.

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?

Gives explicit mode-selection guidance: omit the query to get followed sites, pass one to search all sites. That is clear when-to-use guidance for the tool's own two behaviors, but it offers no guidance about when to pick this over other site-related listing tools.

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