Skip to main content
Glama
routineco

Routine

Official
by routineco

peopleGet

Retrieve contact details by ID from Routine. Simplify access to specific contact information for calendars, tasks, and notes.

Instructions

The contact with the given id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • Executes the tool logic: fetches contact data by ID via RPC call to 'people.get' and formats response as JSON text, with error handling.
    async ({ id }) => {
      try {
        const data = await sendRpcRequest("people.get", [id]);
        return {
          content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
        };
      } catch (error) {
        logger.error("Error fetching people.get: %o", error);
        return {
          content: [
            {
              type: "text",
              text: `Error fetching auth id: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Zod input schema requiring a string 'id' parameter for the people ID.
        {
          /*
    {"$id":"#people-id","$schema":"https://json-schema.org/draft/2019-09/schema","type":"string"}
    */ id: z.string(),
        },
  • src/tools.ts:256-283 (registration)
    Registers the 'peopleGet' tool on the MCP server with name, description, input schema, and handler function.
      server.tool(
        "peopleGet",
        "The contact with the given id.",
        {
          /*
    {"$id":"#people-id","$schema":"https://json-schema.org/draft/2019-09/schema","type":"string"}
    */ id: z.string(),
        },
        async ({ id }) => {
          try {
            const data = await sendRpcRequest("people.get", [id]);
            return {
              content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
            };
          } catch (error) {
            logger.error("Error fetching people.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 fails to describe any behavioral traits—it doesn't indicate whether this is a read-only operation, what happens if the ID is invalid, potential error conditions, or authentication requirements. The description is too vague to inform the agent about how the tool behaves.

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

Conciseness4/5

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

The description is a single, concise sentence that is front-loaded with the core idea. There is no wasted verbiage, making it efficient in terms of length. However, it lacks structural elements like examples or clarifications that could enhance understanding without sacrificing 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 complexity of a retrieval tool with no annotations, no output schema, and poor parameter documentation, the description is incomplete. It doesn't explain what is returned (e.g., contact details), error handling, or usage context, leaving significant gaps for the agent to infer behavior and results.

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, meaning the schema provides no semantic information about the 'id' parameter. The description does not compensate by explaining what the 'id' represents (e.g., a contact identifier, format, or source), leaving the parameter's meaning entirely 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 'The contact with the given id' is a tautology that essentially restates the tool name 'peopleGet' without specifying the action. It lacks a clear verb (like 'retrieve' or 'fetch') and doesn't distinguish this tool from sibling tools like 'peopleByEmail' or 'pageGet'. The purpose is implied but not explicitly stated.

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 sibling tools like 'peopleByEmail' for email-based lookups or 'pageGet' for retrieving pages, nor does it specify prerequisites such as needing a contact ID. The description offers no context for usage decisions.

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