Skip to main content
Glama
routineco

Routine

Official
by routineco

calendarGet

Retrieve calendar details by ID from the Routine MCP server. Use this tool to access specific calendars for managing schedules, tasks, and events efficiently.

Instructions

A calendar.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • Handler function that takes a calendar ID, sends an RPC request to 'calendar.get', and returns the JSON-stringified data or an error message.
    async ({ id }) => {
      try {
        const data = await sendRpcRequest("calendar.get", [id]);
        return {
          content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
        };
      } catch (error) {
        logger.error("Error fetching calendar.get: %o", error);
        return {
          content: [
            {
              type: "text",
              text: `Error fetching auth id: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Input schema defining 'id' as a string using Zod (z.string()), with embedded JSON schema comment.
        {
          /*
    {"$id":"#calendar-id","$schema":"https://json-schema.org/draft/2019-09/schema","type":"string"}
    */ id: z.string(),
        },
  • src/tools.ts:46-73 (registration)
    Registration of the 'calendarGet' tool via server.tool() within registerServerTools, including name, description, schema, and handler.
      server.tool(
        "calendarGet",
        "A calendar.",
        {
          /*
    {"$id":"#calendar-id","$schema":"https://json-schema.org/draft/2019-09/schema","type":"string"}
    */ id: z.string(),
        },
        async ({ id }) => {
          try {
            const data = await sendRpcRequest("calendar.get", [id]);
            return {
              content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
            };
          } catch (error) {
            logger.error("Error fetching calendar.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. However, it gives no information about what the tool does (e.g., read, write, delete), its effects, permissions required, or response format, failing to compensate for the lack of structured data.

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 concise with only two words, the description is under-specified rather than efficiently informative. It lacks any structure or front-loading of key details, making it ineffective despite its 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 unknown complexity (implied by sibling tools like 'calendarAll'), no annotations, no output schema, and a parameter with 0% coverage, the description is completely inadequate. It fails to provide any meaningful information needed for an agent to understand or use the tool correctly.

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 schema has 0% description coverage for its single required parameter 'id', and the description adds no meaning or context about this parameter. It does not explain what 'id' represents (e.g., a calendar identifier) or how to use it, leaving the parameter completely undocumented.

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?

The description 'A calendar.' is a tautology that merely restates the tool name without specifying any action or purpose. It provides no verb or indication of what the tool does (e.g., retrieve, create, update), making it completely uninformative and misleading for an AI agent.

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 offers no guidance on when to use this tool versus alternatives. It does not mention any context, prerequisites, or distinctions from sibling tools like 'calendarAll' or 'eventGet', leaving the agent with no basis for selection.

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