Skip to main content
Glama
routineco

Routine

Official
by routineco

eventGet

Retrieve event details from Routine by providing a unique event ID, enabling streamlined calendar and task management.

Instructions

An event.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • The handler function for the 'eventGet' tool. It takes an 'id' parameter, sends an RPC request to 'event.get' with the id, and returns the JSON-formatted data or an error response.
    async ({ id }) => {
      try {
        const data = await sendRpcRequest("event.get", [id]);
        return {
          content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
        };
      } catch (error) {
        logger.error("Error fetching event.get: %o", error);
        return {
          content: [
            {
              type: "text",
              text: `Error fetching auth id: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Zod schema for the input parameters of the 'eventGet' tool, defining a required 'id' string parameter.
        {
          /*
    {"$id":"#event-id","$schema":"https://json-schema.org/draft/2019-09/schema","type":"string"}
    */ id: z.string(),
        },
  • src/tools.ts:120-147 (registration)
    The server.tool call that registers the 'eventGet' MCP tool with its description, input schema, and handler function.
      server.tool(
        "eventGet",
        "An event.",
        {
          /*
    {"$id":"#event-id","$schema":"https://json-schema.org/draft/2019-09/schema","type":"string"}
    */ id: z.string(),
        },
        async ({ id }) => {
          try {
            const data = await sendRpcRequest("event.get", [id]);
            return {
              content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
            };
          } catch (error) {
            logger.error("Error fetching event.get: %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)
    Calls registerServerTools which includes the registration of the 'eventGet' tool among others on the MCP server.
    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. 'An event.' gives no indication of whether this is a read, write, or destructive operation, what permissions are required, what happens on success/failure, or any rate limits. It fails to describe any behavioral traits.

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 two words, this is under-specification rather than effective brevity. The description is too sparse to be useful, failing to convey essential information that would help an agent use the tool correctly.

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 no annotations, no output schema, and a parameter with 0% schema coverage, the description is completely inadequate. It doesn't explain what the tool does, how to use it, what it returns, or any behavioral characteristics, leaving critical gaps for agent understanding.

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 description provides no information about parameters. With 0% schema description coverage and one required parameter 'id', the description doesn't explain what 'id' represents, its format, or where to obtain it. It adds zero value beyond the bare schema.

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 'An event.' is a tautology that merely restates the tool name 'eventGet' without specifying what action it performs. It doesn't indicate whether this retrieves, creates, modifies, or deletes events, nor does it distinguish it from sibling tools like 'eventDay' or 'eventTimeline'.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention context, prerequisites, or exclusions, leaving the agent with no information about appropriate usage scenarios compared to sibling tools like 'eventDay' or 'calendarGet'.

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