Skip to main content
Glama

linear_getViewer

Retrieve information about the currently authenticated user in Linear to verify identity and access permissions for project management tasks.

Instructions

Get information about the currently authenticated user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for the 'linear_getViewer' tool. It wraps the call to linearService.getUserInfo() with error handling.
    export function handleGetViewer(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          return await linearService.getUserInfo();
        } catch (error) {
          logError('Error getting viewer information', error);
          throw error;
        }
      };
    }
  • The MCPToolDefinition for 'linear_getViewer', specifying no input parameters and the expected output schema for viewer information.
    export const getViewerToolDefinition: MCPToolDefinition = {
      name: 'linear_getViewer',
      description: 'Get information about the currently authenticated user',
      input_schema: {
        type: 'object',
        properties: {},
      },
      output_schema: {
        type: 'object',
        properties: {
          id: { type: 'string' },
          name: { type: 'string' },
          email: { type: 'string' },
          active: { type: 'boolean' },
          displayName: { type: 'string' },
          organization: {
            type: 'object',
            properties: {
              id: { type: 'string' },
              name: { type: 'string' },
            },
          },
        },
      },
    };
  • Registration of the 'linear_getViewer' handler within the registerToolHandlers function, mapping the tool name to the handler.
    // User tools
    linear_getViewer: handleGetViewer(linearService),
    linear_getOrganization: handleGetOrganization(linearService),
    linear_getUsers: handleGetUsers(linearService),
    linear_getLabels: handleGetLabels(linearService),
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. It states this is a 'Get' operation, implying read-only behavior, but doesn't mention authentication requirements, rate limits, error conditions, or what happens if no user is authenticated. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves in edge cases.

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 front-loads the essential information ('Get information about the currently authenticated user') with zero wasted words. Every part of the sentence earns its place by specifying the action, resource, and context efficiently.

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

Completeness3/5

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

Given the tool's simplicity (0 parameters, no output schema), the description is adequate for basic understanding but lacks depth. It doesn't explain what information is returned (e.g., user ID, email, permissions) or potential authentication requirements, which could be important for an agent. With no annotations or output schema, more context would be helpful despite the low complexity.

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's no need for parameter documentation in the description. The description appropriately doesn't mention parameters, focusing instead on the tool's purpose. A baseline of 4 is justified since it doesn't need to compensate for any parameter gaps.

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 verb ('Get') and resource ('information about the currently authenticated user'), making the purpose immediately understandable. It distinguishes itself from sibling tools like linear_getUsers or linear_getOrganization by focusing specifically on the authenticated user rather than general user/organization data. However, it doesn't specify what type of information is retrieved (profile, permissions, etc.), keeping it from 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by specifying 'currently authenticated user,' suggesting this tool should be used when the agent needs to identify who is logged in. However, it doesn't explicitly state when to use this versus alternatives like linear_getUsers (which lists all users) or provide any exclusions or prerequisites. The guidance is present but minimal.

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/tacticlaunch/mcp-linear'

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