Skip to main content
Glama
routineco

Routine

Official
by routineco

pageGet

Retrieve a specific page by ID from Routine's MCP server to manage calendars, tasks, or notes efficiently.

Instructions

Get a page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • The handler function for the 'pageGet' tool. It takes a page 'id' parameter, sends an RPC request to 'page.get' via sendRpcRequest, and returns the page data as a JSON-formatted text content block or an error response if the request fails.
    async ({ id }) => {
      try {
        const data = await sendRpcRequest("page.get", [id]);
        return {
          content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
        };
      } catch (error) {
        logger.error("Error fetching page.get: %o", error);
        return {
          content: [
            {
              type: "text",
              text: `Error fetching auth id: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Zod schema defining the input parameter for 'pageGet': 'id' as a required string (page identifier). The comment contains the corresponding JSON schema.
        {
          /*
    {"$id":"#page-id","$schema":"https://json-schema.org/draft/2019-09/schema","type":"string"}
    */ id: z.string(),
        },
  • src/tools.ts:198-225 (registration)
    Registration of the 'pageGet' tool on the MCP server using server.tool(). Includes the tool name, description, input schema validator, and the handler function.
      server.tool(
        "pageGet",
        "Get a page.",
        {
          /*
    {"$id":"#page-id","$schema":"https://json-schema.org/draft/2019-09/schema","type":"string"}
    */ id: z.string(),
        },
        async ({ id }) => {
          try {
            const data = await sendRpcRequest("page.get", [id]);
            return {
              content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
            };
          } catch (error) {
            logger.error("Error fetching page.get: %o", error);
            return {
              content: [
                {
                  type: "text",
                  text: `Error fetching auth id: ${error instanceof Error ? error.message : String(error)}`,
                },
              ],
              isError: true,
            };
          }
        }
      );
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. 'Get a page' implies a read operation, but it doesn't specify whether this requires authentication, what happens on failure, if there are rate limits, or the format of the returned data. For a tool with zero annotation coverage, this is a significant gap in transparency.

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

Conciseness5/5

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

The description is extremely concise with a single sentence 'Get a page.', which is front-loaded and wastes no words. While under-specified, it efficiently conveys the basic action without unnecessary elaboration, earning full marks for brevity.

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 tool's complexity (1 parameter, no annotations, no output schema), the description is incomplete. It doesn't explain what a 'page' is in this context, how to use the tool effectively, or what to expect in return. For a tool with minimal structured data, the description should provide more context but fails to do so.

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?

The input schema has 1 parameter with 0% description coverage, and the description adds no meaning beyond the schema. It doesn't explain what the 'id' parameter represents, its format, or how to obtain it. With low schema coverage, the description fails to compensate, leaving the parameter undocumented.

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 'Get a page' is a tautology that restates the tool name 'pageGet' with minimal elaboration. While it indicates the verb 'Get' and resource 'page', it lacks specificity about what kind of page or what information is retrieved. It doesn't distinguish this tool from sibling tools like 'pageAll' or 'eventGet', leaving the purpose vague.

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. It doesn't mention sibling tools like 'pageAll' for listing pages or 'eventGet' for events, nor does it specify prerequisites or contexts for usage. This absence of guidance makes it misleading for an AI agent to select the correct tool.

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