search_sheets
Search sheets by keyword query, with an optional limit on the number of results returned.
Instructions
シート検索
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | 検索キーワード | |
| limit | No | 取得件数(デフォルト: 20) |
Search sheets by keyword query, with an optional limit on the number of results returned.
シート検索
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | 検索キーワード | |
| limit | No | 取得件数(デフォルト: 20) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description fails to disclose any behavioral traits (e.g., read-only, pagination, result format). The description is essentially empty of behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely brief (one phrase), but it is under-specified rather than concise. It does not provide enough information to be useful.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a search tool with two parameters and no annotations or output schema, the description is completely inadequate. It does not explain behavior, output, or limitations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, and the parameter descriptions are in Japanese. The tool description adds no extra meaning beyond the schema, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description is a single Japanese phrase 'シート検索' meaning 'sheet search'. It indicates the action and resource but is vague, lacking differentiation from siblings like 'search_sessions' or 'find_solution'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool vs alternatives. The sibling list includes many search-related tools, but no context or exclusions are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/asicojp/sparksheets-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server