Skip to main content
Glama
routineco

Routine

Official
by routineco

pageAll

Retrieve and manage all pages within Routine's platform to organize calendars, tasks, and notes efficiently in one centralized interface.

Instructions

All pages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'pageAll' MCP tool. It calls the underlying RPC 'page.all' via sendRpcRequest with no parameters, stringifies the result as JSON, and returns it as text content. Includes error handling returning an error message.
    server.tool("pageAll", "All pages.", {}, async ({}) => {
      try {
        const data = await sendRpcRequest("page.all", []);
        return {
          content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
        };
      } catch (error) {
        logger.error("Error fetching page.all: %o", error);
        return {
          content: [
            {
              type: "text",
              text: `Error fetching auth id: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    });
  • src/index.ts:234-234 (registration)
    Call to registerServerTools which registers the pageAll tool (among others) on the MCP server.
    registerServerTools(server, sendRpcRequest, logger);
  • src/tools.ts:5-5 (registration)
    The registerServerTools function that contains the server.tool registration for pageAll.
    export function registerServerTools(server, sendRpcRequest, logger) {
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'All pages' gives no indication of whether this is a read or write operation, what permissions might be required, whether it's safe or destructive, or what the expected output format might be. The description fails to provide any 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.

Conciseness2/5

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

While technically concise with just two words, this represents under-specification rather than effective conciseness. The description fails to provide essential information that would help an agent understand and use the tool correctly. Every word should earn its place, but here the words don't provide meaningful guidance.

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?

Given the lack of annotations, no output schema, and a minimal description, this is completely inadequate for a tool that presumably returns some kind of data. The description doesn't explain what 'pages' are, what format they're returned in, or what the scope of 'all' encompasses. For a tool with no structured metadata, the description should provide much more context.

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

Parameters4/5

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

The tool has zero parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description doesn't need to compensate for any parameter gaps. The baseline for zero parameters with complete schema coverage is 4, as there's nothing additional the description could reasonably add about parameters.

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

Purpose2/5

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

The description 'All pages' is a tautology that essentially restates the tool name 'pageAll'. It doesn't specify what action the tool performs (list? retrieve? display?) or what resource 'pages' refers to. While it indicates the tool deals with pages, it lacks a clear verb and doesn't distinguish from sibling tools like 'pageGet'.

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?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of context, prerequisites, or comparison with sibling tools like 'pageGet'. The agent receives no help in determining appropriate usage scenarios.

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/routineco/mcp-server'

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