Skip to main content
Glama

linear_getOrganization

Retrieve details about your Linear organization to manage projects, teams, and issues effectively.

Instructions

Get information about the current Linear organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for the 'linear_getOrganization' tool. It wraps the call to linearService.getOrganizationInfo() with error handling.
    /**
     * Handler for getting organization information
     */
    export function handleGetOrganization(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          return await linearService.getOrganizationInfo();
        } catch (error) {
          logError('Error getting organization information', error);
          throw error;
        }
      };
    }
  • The MCPToolDefinition for 'linear_getOrganization', specifying input (empty) and output schemas.
     * Tool definition for getting organization information
     */
    export const getOrganizationToolDefinition: MCPToolDefinition = {
      name: 'linear_getOrganization',
      description: 'Get information about the current Linear organization',
      input_schema: {
        type: 'object',
        properties: {},
      },
      output_schema: {
        type: 'object',
        properties: {
          id: { type: 'string' },
          name: { type: 'string' },
          urlKey: { type: 'string' },
          logoUrl: { type: 'string' },
        },
      },
    };
  • Registration of the 'linear_getOrganization' handler in the tool handlers map returned by registerToolHandlers.
    // 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 the full burden of behavioral disclosure. It states it 'gets' information, implying a read-only operation, but doesn't clarify aspects like authentication requirements, rate limits, error conditions, or what 'current' means in context (e.g., based on API token). This leaves significant gaps for an agent to rely on.

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 with no wasted words. It front-loads the core action ('Get information') and specifies the target ('current Linear organization'), making it efficient and easy to parse.

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, no annotations), the description is minimally adequate. It explains what the tool does but lacks details on behavior, output format, or usage context. For a read-only tool with no parameters, this is acceptable but leaves room for improvement in guiding an agent.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add any parameter details, which is appropriate here. A baseline of 4 is applied as it meets the expectation for a parameterless tool without redundancy.

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 current Linear organization'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'linear_getViewer' (which might return user-specific data) or 'linear_getTeams' (which returns team-level data), 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 (e.g., authentication context), compare it to similar sibling tools (like 'linear_getViewer' for user info), or specify use cases (e.g., for organization-level settings or metadata).

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