Skip to main content
Glama
Office MCP Server

Office MCP Server

by hvkshetry

files_map_sharepoint_path

Map a SharePoint web URL to its corresponding local sync path to locate synced files and folders on your device.

Instructions

Map SharePoint webUrl to local sync path

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": {
      "webUrl": "<webUrl>"
    },
    "name": "files_map_sharepoint_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
webUrlYesSharePoint web URL to map to local sync path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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. It states the core mapping behavior but does not explain what happens when the URL is not synced locally, whether the path must exist, or what the result looks like on failure.

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?

The description is a single front-loaded sentence with no unnecessary wording. Every word contributes to the stated transformation.

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 simple one-parameter lookup tool, the description identifies the input and intended output concept. However, with no output schema, it omits return-value details and failure conditions that would help an agent use it confidently.

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% for the single webUrl parameter, so the schema already documents it adequately. The description adds no meaning beyond restating the mapping from SharePoint webUrl to local sync path.

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?

The description states a specific verb and resource: mapping a SharePoint webUrl to a local sync path. It is clear enough for an agent to understand the transformation being performed, though it does not explicitly distinguish itself from broader file-related siblings.

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 explicit guidance on when to use this tool versus alternatives, nor any prerequisites such as requiring the SharePoint library to be synced locally. Usage is only implied by the mapping purpose.

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