Skip to main content
Glama
Sign In
sharepoint-mcp

sharepoint-mcp

by ravikant1918
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get_File_Metadata

Retrieve all SharePoint list-item metadata fields for a document, including custom and system properties.

Instructions

Retrieve all SharePoint list-item metadata fields for a document.

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": {
      "folder_name": "<folder_name>",
      "file_name": "<file_name>"
    },
    "name": "Get_File_Metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
folder_nameYes
file_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations provided, so description must cover behavioral traits. It only states the core action without disclosing read-only nature, error handling, authentication needs, or performance characteristics. For a retrieval tool, this is insufficient.

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 a single concise sentence, front-loading the purpose. However, it could be slightly expanded without losing conciseness to include parameter hints.

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

Completeness2/5

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

No output schema, so description must explain return values. It only says 'all metadata fields' without format or example. Error cases and parameter constraints are missing, leaving the agent underinformed.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not mention folder_name or file_name. The description provides no additional meaning beyond the schema, failing to compensate for low coverage as required.

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 action 'Retrieve' and the resource 'all SharePoint list-item metadata fields for a document', distinguishing it from siblings like Get_Document_Content (content) and Update_File_Metadata (update).

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?

No guidance on when to use this tool versus alternatives such as Get_Document_Content for content or Search_SharePoint for searching. The description does not provide context for optimal usage.

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