zen_select_page
Select a page or tab by index from a list to set it as the active target.
Instructions
Select a page/tab by index (from zen_list_pages) as the active target
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| index | Yes | Page index |
Select a page or tab by index from a list to set it as the active target.
Select a page/tab by index (from zen_list_pages) as the active target
| Name | Required | Description | Default |
|---|---|---|---|
| index | Yes | Page index |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears full responsibility. It explains that the tool sets the page as the 'active target', implying a focus change, but lacks details on side effects, error handling, or prerequisites.
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 a single sentence of 12 words, efficiently conveying the tool's purpose and context with no redundant information.
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?
Given the tool's simplicity (one parameter, no output schema), the description is mostly complete. It could be slightly improved by mentioning behavior for invalid indices.
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?
With 100% schema coverage, baseline is 3. The description adds value by specifying that the index comes from 'zen_list_pages', which clarifies the parameter's origin and usage.
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 clearly states the action ('Select') and the resource ('page/tab by index'), and explicitly references the sibling tool 'zen_list_pages' to differentiate its source of input.
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?
The description implies that the tool should be used after listing pages with 'zen_list_pages', providing clear context. However, it does not explicitly state when not to use it or mention alternatives.
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/sh6drack/zen-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server