Skip to main content
Glama

toggl_check_auth

Verify Toggl API connectivity and authentication status to ensure proper integration with time tracking workflows.

Instructions

Verify Toggl API connectivity and authentication is valid

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic for the 'toggl_check_auth' tool within the CallToolRequestSchema switch statement. It verifies authentication by calling api.getMe() and api.getWorkspaces(), masks the user's email for privacy, and returns a JSON response with authentication status, masked user info, and list of workspaces.
    case 'toggl_check_auth': {
      const me = await api.getMe();
      const workspaces = await api.getWorkspaces();
      const maskEmail = (e?: string) => {
        if (!e) return undefined as unknown as string;
        const [user, domain] = e.split('@');
        if (!domain) return '***';
        const u = user.length <= 2 ? '*'.repeat(user.length) : `${user[0]}***${user.slice(-1)}`;
        return `${u}@${domain}`;
      };
      return {
        content: [{
          type: 'text',
          text: JSON.stringify({
            authenticated: true,
            user: {
              id: (me as any).id,
              email: maskEmail((me as any).email),
              fullname: (me as any).fullname
            },
            workspaces: workspaces.map(w => ({ id: w.id, name: w.name })),
          }, null, 2)
        }]
      };
    }
  • Tool schema and registration entry for 'toggl_check_auth' in the tools array. Defines the tool name, description, and empty input schema (no parameters required). This array is served via the ListToolsRequestSchema handler.
    {
      name: 'toggl_check_auth',
      description: 'Verify Toggl API connectivity and authentication is valid',
      inputSchema: {
        type: 'object',
        properties: {},
        required: []
      },
    },
  • src/index.ts:386-388 (registration)
    Registration of the tool list handler using server.setRequestHandler for ListToolsRequestSchema, which returns the 'tools' array containing the 'toggl_check_auth' schema.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
Behavior2/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. It mentions verifying connectivity and authentication but lacks details on what 'valid' means, how errors are handled, or what the output might be (e.g., success/failure status). For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 a single, clear sentence that efficiently conveys the tool's purpose without unnecessary words. It is front-loaded and to the point, making it easy to parse quickly. Every part of the sentence earns its place by directly contributing to understanding the tool's function.

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 the lack of annotations and output schema, the description is incomplete for a tool that verifies critical aspects like API connectivity and authentication. It doesn't explain what happens upon success or failure, potential error messages, or any side effects. For a tool with no structured data to supplement it, this leaves too much ambiguity for effective use.

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, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately avoids mentioning any. This meets the baseline for tools with no parameters, as it doesn't mislead or omit necessary information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Verify Toggl API connectivity and authentication is valid'. It specifies the action (verify) and the target (Toggl API connectivity and authentication), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from siblings like 'toggl_warm_cache', which might also involve connectivity checks, so it falls short of a perfect score.

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 alternatives. It doesn't mention prerequisites, such as whether authentication must be set up first, or suggest scenarios like troubleshooting connectivity issues. Without this context, users might struggle to determine the appropriate time to invoke it among the 13 sibling tools.

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

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/verygoodplugins/mcp-toggl'

If you have feedback or need assistance with the MCP directory API, please join our Discord server