Skip to main content
Glama
routineco

Routine

Official
by routineco

authProfile

Manage and authenticate user identities within the Routine system to interact with calendars, tasks, and notes efficiently.

Instructions

Main user identity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'authProfile' tool. It calls sendRpcRequest('auth.profile', []) to fetch the main user identity and returns it as a formatted JSON text response, or an error if the request fails.
    server.tool("authProfile", "Main user identity.", {}, async ({}) => {
      try {
        const data = await sendRpcRequest("auth.profile", []);
        return {
          content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
        };
      } catch (error) {
        logger.error("Error fetching auth.profile: %o", error);
        return {
          content: [
            {
              type: "text",
              text: `Error fetching auth id: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    });
  • src/tools.ts:6-24 (registration)
    The server.tool call registers the 'authProfile' tool with an empty input schema ({}), description 'Main user identity.', and the handler function.
    server.tool("authProfile", "Main user identity.", {}, async ({}) => {
      try {
        const data = await sendRpcRequest("auth.profile", []);
        return {
          content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
        };
      } catch (error) {
        logger.error("Error fetching auth.profile: %o", error);
        return {
          content: [
            {
              type: "text",
              text: `Error fetching auth id: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    });
  • src/index.ts:234-235 (registration)
    Calls registerServerTools which includes the registration of the authProfile tool among others.
    registerServerTools(server, sendRpcRequest, logger);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal information. 'Main user identity' doesn't indicate whether this is a read operation, write operation, or something else. It doesn't disclose authentication requirements, rate limits, side effects, or what the tool actually returns. For a tool with zero annotation coverage, this description is inadequate.

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

Conciseness3/5

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

The description is extremely concise at just three words, but this brevity comes at the cost of meaningful information. While it's not verbose or repetitive, it's under-specified rather than appropriately concise. The single phrase doesn't provide enough substance to be considered well-structured or helpful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that this tool has no annotations, no output schema, and a minimal description, the overall context is severely lacking. The description doesn't explain what 'Main user identity' means in practical terms, what the tool returns, or how it should be used in relation to the many sibling tools. For a tool that presumably handles authentication or user identity (a critical function), this description is incomplete.

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 0 parameters with 100% schema description coverage, so the baseline is 4. The description doesn't need to compensate for undocumented parameters since there are none. While the description doesn't add parameter-specific information (because there are no parameters), it doesn't detract from the complete schema coverage either.

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 'Main user identity' is a tautology that essentially restates the tool name 'authProfile' without specifying what the tool actually does. It doesn't indicate whether this retrieves, sets, verifies, or manages authentication profiles. The description lacks a clear verb-action-resource structure that would explain the tool's function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/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 the 16 sibling tools listed. There's no indication of whether this should be called before other operations, what context it's appropriate for, or what alternatives might exist for authentication or profile management. The agent receives no usage context from this description.

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