Skip to main content
Glama

pylon_get_account

Retrieve detailed information about a customer account using its ID. Access key account data to manage support interactions efficiently.

Instructions

Get account details by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe account ID or external ID

Implementation Reference

  • The tool registration and handler for 'pylon_get_account'. Calls client.getAccount(id), transforms via toAccountMinimal, and returns JSON result.
    server.tool(
    	'pylon_get_account',
    	'Get account details by ID.',
    	{
    		id: z.string().describe('The account ID or external ID'),
    	},
    	async ({ id }) => {
    		const result = await client.getAccount(id);
    		// Return minimal fields to reduce context size
    		const account = toAccountMinimal(result.data as unknown as Record<string, unknown>);
    		return {
    			content: [{ type: 'text', text: JSON.stringify(account, null, 2) }],
    		};
    	},
    );
  • src/index.ts:235-249 (registration)
    The server.tool() call that registers 'pylon_get_account' with MCP.
    server.tool(
    	'pylon_get_account',
    	'Get account details by ID.',
    	{
    		id: z.string().describe('The account ID or external ID'),
    	},
    	async ({ id }) => {
    		const result = await client.getAccount(id);
    		// Return minimal fields to reduce context size
    		const account = toAccountMinimal(result.data as unknown as Record<string, unknown>);
    		return {
    			content: [{ type: 'text', text: JSON.stringify(account, null, 2) }],
    		};
    	},
    );
  • The AccountMinimalSchema defining the shape of the returned account data (id, name, primary_domain, owner_id, tags).
    export const AccountMinimalSchema = z.object({
    	id: z.string(),
    	name: z.string(),
    	primary_domain: z.string().nullable().optional(),
    	owner_id: z.string().nullable().optional(),
    	tags: z.array(z.string()).nullable().optional(),
    });
  • The toAccountMinimal helper function that transforms raw API response to AccountMinimal format.
    export function toAccountMinimal(raw: Record<string, unknown>): AccountMinimal {
    	const owner = raw['owner'] as { id?: string } | null | undefined;
    	return {
    		id: raw['id'] as string,
    		name: raw['name'] as string,
    		primary_domain: raw['primary_domain'] as string | null | undefined,
    		owner_id: owner?.id ?? (raw['owner_id'] as string | null | undefined),
    		tags: raw['tags'] as string[] | null | undefined,
    	};
    }
  • The getAccount method on PylonClient that performs the HTTP GET request to /accounts/{id}.
    async getAccount(id: string): Promise<SingleResponse<Account>> {
    	return this.request<SingleResponse<Account>>('GET', `/accounts/${id}`);
    }
Behavior2/5

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

No annotations provided; description lacks disclosure of behavioral traits like error handling, rate limits, or authentication requirements. Only states a read operation.

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

Conciseness4/5

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

Single, direct sentence with no unnecessary words. Efficient for a simple get-by-ID tool, though could be slightly more informative without sacrificing conciseness.

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?

No output schema; description does not mention return values or structure. Adequate for a basic read operation, but misses opportunity to clarify what 'account details' includes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% coverage with parameter description 'The account ID or external ID'. The tool description adds no extra meaning, so baseline 3 is appropriate.

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

Purpose5/5

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

Description clearly states the action ('Get'), resource ('account details'), and method ('by ID'). Distinct from sibling tools like pylon_get_contact or pylon_get_issue.

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?

No guidance on when to use this tool versus alternatives like pylon_list_accounts or pylon_search_accounts. No context about prerequisites or use cases.

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