Skip to main content
Glama
MartinCley

SharePoint-Cleyrop MCP

by MartinCley

sharepoint_login_finish

Completes SharePoint authentication by storing the user's refresh token, allowing immediate access to sites and files.

Instructions

Finalise la connexion SharePoint et mémorise l'accès de l'utilisateur.

APPELLE CET OUTIL SANS AUCUN ARGUMENT dès que l'utilisateur indique qu'il a terminé l'étape navigateur — par exemple « c'est bon », « j'ai validé », « connecté », « go ». Le serveur retrouve automatiquement la connexion en cours grâce à l'identité de l'utilisateur. Ne demande JAMAIS de login_id à l'utilisateur : laisse le paramètre vide (il n'est utile qu'en mode local sans identité).

En cas de succès, le refresh token est mémorisé côté serveur pour l'utilisateur courant : il n'a en principe rien à copier, il peut enchaîner directement (recherche de sites, transfert...).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
login_idNooptionnel — ne le renseigner qu'en mode local (stdio).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Discloses that refresh token is stored server-side, user need not copy anything, and connection is auto-retrieved by identity. No annotations provided, so description carries full burden.

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?

Well-structured with main purpose first, then imperative instructions. Slightly verbose but clear and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers usage, success behavior, side effects (token storage), and mentions output schema exists. Adequate for a simple tool.

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

Parameters5/5

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

Explains login_id is optional and only for local mode, adding meaning beyond schema's description. Agent knows not to request it from user.

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?

Description clearly states the tool finalizes SharePoint login and memorizes user access, distinguishing it from siblings like sharepoint_login_start.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs to call without arguments after user completes browser step, and warns not to ask for login_id. Provides clear context.

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/MartinCley/Sharepoint-MCP'

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