Skip to main content
Glama
penysho

Google Docs MCP Server

by penysho

search_google_documents

Search and retrieve specific content from Google Docs using a query. Specify the maximum number of results to streamline document discovery and access relevant information efficiently.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxResultsNo取得する最大結果数(デフォルト: 10)
queryYes検索クエリ

Implementation Reference

  • The core handler function that executes the Google Documents search using the Google Docs service.
    protected async executeInternal(args: {
    	query: string;
    	maxResults?: number;
    }): Promise<McpToolResponse> {
    	// 引数検証
    	this.validateArgs(args, ["query"]);
    
    	const { query, maxResults = 10 } = args;
    	this.logger.info(
    		`ドキュメント検索開始: クエリ="${query}", 最大結果数=${maxResults}`,
    	);
    
    	try {
    		// Google Docsサービスを取得
    		const docsService = await this.serviceContainer.getGoogleDocsService();
    
    		// ドキュメントを検索
    		const results = await docsService.searchForDocuments(query, maxResults);
    
    		this.logger.info(
    			`ドキュメント検索完了: クエリ="${query}", 結果件数=${results.length}`,
    		);
    
    		return this.createSuccessResponse(JSON.stringify(results, null, 2));
    	} catch (error) {
    		this.logger.error(`ドキュメント検索エラー: クエリ="${query}"`, error);
    		throw error; // BaseMcpToolでエラーハンドリング
    	}
    }
  • Zod schema defining the input parameters: query (required string) and optional maxResults (number).
    get schema() {
    	return {
    		query: z.string().describe("検索クエリ"),
    		maxResults: z
    			.number()
    			.optional()
    			.describe("取得する最大結果数(デフォルト: 10)"),
    	};
    }
  • Constructor calls super to register the tool with name 'search_google_documents'.
    constructor(serviceContainer: IServiceContainer) {
    	super("search_google_documents", serviceContainer);
    }
  • Instantiates and registers the SearchDocumentsTool in the default tools registry.
    this.registerTool(new SearchDocumentsTool(this.serviceContainer));
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/penysho/docs-mcp'

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