Skip to main content
Glama
BrianCusack

Sharepoint MCP Server

by BrianCusack

search-documents

Search and retrieve Sharepoint documents using a query, enabling quick access to organizational content via the Microsoft Graph API for efficient document management.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxResultsNoMaximum number of results to return (as a string)
queryYesSearch query to find documents

Implementation Reference

  • The handler function for the "search-documents" tool. It lists all drive items from the SharePoint drive, filters those whose name includes the provided query, limits the results to the specified maxResults, and returns them as a JSON string in text content. Handles errors by returning an error message.
      try {
        const driveRef = createDriveRef(siteRef, driveId);
        const driveItems = await listDriveItems(driveRef);
        const results = driveItems.filter((item: any) => item.name.includes(query)).slice(0, parseInt(maxResults.toString(), 10));
        return {
          content: [{
            type: "text",
            text: JSON.stringify(results, null, 2) // Ensure this is a valid string
          }]
        };
      } catch (error) {
        return {
          content: [{
            type: "text",
            text: `Error searching documents: ${error}`
          }],
          isError: true
        };
      }
    }
  • The input schema defined using Zod for the "search-documents" tool, specifying the required 'query' parameter and optional 'maxResults'.
      query: z.string().describe("Search query to find documents"),
      maxResults: z.string().optional().describe("Maximum number of results to return (as a string)")
    },
    async ({ query, maxResults = 10 }) => {
  • src/index.ts:93-119 (registration)
    The registration of the "search-documents" tool using McpServer.tool(), including the tool name, input schema, and inline handler function.
      "search-documents",
      {
        query: z.string().describe("Search query to find documents"),
        maxResults: z.string().optional().describe("Maximum number of results to return (as a string)")
      },
      async ({ query, maxResults = 10 }) => {
        try {
          const driveRef = createDriveRef(siteRef, driveId);
          const driveItems = await listDriveItems(driveRef);
          const results = driveItems.filter((item: any) => item.name.includes(query)).slice(0, parseInt(maxResults.toString(), 10));
          return {
            content: [{
              type: "text",
              text: JSON.stringify(results, null, 2) // Ensure this is a valid string
            }]
          };
        } catch (error) {
          return {
            content: [{
              type: "text",
              text: `Error searching documents: ${error}`
            }],
            isError: true
          };
        }
      }
    );
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Related 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/BrianCusack/mcpsharepoint'

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