Skip to main content
Glama
XMV-Solutions-GmbH

mcp-server-sharepoint

sp_auth_status

Read-onlyIdempotent

Check SharePoint authentication status. Returns signed-in, pending device code, or no token state, enabling the agent to proceed, wait, or start login.

Instructions

Return the current sign-in state for profile (default 'default'). Three states the agent can act on directly:

  • 'signed_in' — valid token on disk (regardless of how it got there: CLI login, prior tool-flow, or just refreshed silently). signed_in_user_upn populated. The agent can proceed.

  • 'pending' — Device Code flow in progress. user_code, verification_url, time_remaining_s populated.

  • 'none' — no token, no flow. Agent should call sp_auth_begin.

Recently-terminal sessions (expired / failed / cancelled) surface their error via the error field instead of falling back to 'none' — so the agent can render a specific failure message.

AGENT_INSTRUCTIONS: When status='pending', present the verification code to the user inside a fenced code block (so it can be copied with one click) and present the verification URL as a plain markdown link on its own line. Do not paraphrase, do not embed the code inside prose, do not wrap the URL in bold. Same format as sp_auth_begin.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds context about terminal states (expired/failed/cancelled) surfacing errors via the `error` field, which is beyond annotation information. No contradictions.

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?

The description is front-loaded with the main purpose, then details states and agent instructions. It is slightly verbose but well-structured and each sentence serves a purpose. Could be trimmed slightly without losing value.

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?

Given the presence of an output schema (implied), the description adequately covers the return states and their implications for agent action. It provides sufficient context for a tool with one optional parameter.

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 0%, so the description must compensate. It explains the 'profile' parameter and its default value, but does not provide allowed values or further syntax details. This adds some meaning but leaves gaps.

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 clearly states that it returns the current sign-in state for a profile, with specific states explained. It distinguishes itself from sibling tool sp_auth_begin by indicating when to use that tool instead.

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 provides explicit instructions for each state, including agent instructions for presenting the pending verification code. It references sp_auth_begin for the 'none' state, but does not elaborate on other alternatives or when not to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/XMV-Solutions-GmbH/sharepoint-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server