Skip to main content
Glama

pylon_get_organization

Retrieve details about your Pylon organization, including account information and settings, to manage customer support operations.

Instructions

Get information about your Pylon organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the pylon_get_organization tool. Fetches organization data using PylonClient.getMe() and returns it formatted as JSON text content.
    async () => {
    	const result = await client.getMe();
    	return {
    		content: [{ type: 'text', text: JSON.stringify(result.data, null, 2) }],
    	};
    },
  • src/index.ts:26-36 (registration)
    Registers the pylon_get_organization tool with the MCP server, providing name, description, empty input schema, and inline handler.
    server.tool(
    	'pylon_get_organization',
    	'Get information about your Pylon organization',
    	{},
    	async () => {
    		const result = await client.getMe();
    		return {
    			content: [{ type: 'text', text: JSON.stringify(result.data, null, 2) }],
    		};
    	},
    );
  • PylonClient.getMe() helper method that performs the API GET request to '/me' to retrieve organization information.
    async getMe(): Promise<SingleResponse<Organization>> {
    	return this.request<SingleResponse<Organization>>('GET', '/me');
    }
  • TypeScript interface defining the structure of the Organization object returned by the tool.
    export interface Organization {
    	id: string;
    	name: string;
    }
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 'Get information' which implies a read-only operation, but doesn't specify aspects like authentication needs, rate limits, or what type of information is returned. This is a significant gap for a tool with zero annotation coverage.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 tool's simplicity (0 parameters, no output schema), the description is incomplete. It doesn't explain what 'information' includes, such as organization name, settings, or metadata, leaving the agent unsure of the return value. With no annotations or output schema, more detail is needed for adequate context.

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 schema fully documents the lack of inputs. The description doesn't need to add parameter details, and it doesn't contradict the schema. A baseline of 4 is appropriate as no parameters are present.

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 the resource 'information about your Pylon organization', making the purpose understandable. However, it doesn't differentiate from sibling tools like 'pylon_get_account' or 'pylon_get_team', which follow the same pattern for different resources, so it lacks sibling distinction.

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 context, prerequisites, or exclusions, such as whether it's for retrieving general organization details versus specific data from other get tools. This leaves the agent without usage direction.

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/JustinBeckwith/pylon-mcp'

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