Skip to main content
Glama

pylon_get_contact

Retrieve contact details by providing the contact ID.

Instructions

Get contact details by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe contact ID

Implementation Reference

  • The tool handler for 'pylon_get_contact'. It accepts a contact ID, calls client.getContact(id), transforms the result using toContactMinimal(), and returns the contact as formatted JSON.
    server.tool(
    	'pylon_get_contact',
    	'Get contact details by ID.',
    	{
    		id: z.string().describe('The contact ID'),
    	},
    	async ({ id }) => {
    		const result = await client.getContact(id);
    		// Return minimal fields to reduce context size
    		const contact = toContactMinimal(result.data as unknown as Record<string, unknown>);
    		return {
    			content: [{ type: 'text', text: JSON.stringify(contact, null, 2) }],
    		};
    	},
    );
  • ContactMinimalSchema – defines the shape of the contact data returned by the tool (id, name, email, account_id, portal_role).
    export const ContactMinimalSchema = z.object({
    	id: z.string(),
    	name: z.string(),
    	email: z.string().nullable().optional(),
    	account_id: z.string().nullable().optional(),
    	portal_role: z.string().nullable().optional(),
    });
  • toContactMinimal() – transforms raw API response to ContactMinimal format used by the tool handler.
    export function toContactMinimal(raw: Record<string, unknown>): ContactMinimal {
    	const account = raw['account'] as { id?: string } | null | undefined;
    	return {
    		id: raw['id'] as string,
    		name: raw['name'] as string,
    		email: raw['email'] as string | null | undefined,
    		account_id: account?.id ?? (raw['account_id'] as string | null | undefined),
    		portal_role: raw['portal_role'] as string | null | undefined,
    	};
    }
  • PylonClient.getContact() – makes a GET request to /contacts/{id} to fetch a single contact from the Pylon API.
    async getContact(id: string): Promise<SingleResponse<Contact>> {
    	return this.request<SingleResponse<Contact>>('GET', `/contacts/${id}`);
    }
  • src/index.ts:425-439 (registration)
    The tool registration via server.tool('pylon_get_contact', ...) with schema for the 'id' parameter.
    server.tool(
    	'pylon_get_contact',
    	'Get contact details by ID.',
    	{
    		id: z.string().describe('The contact ID'),
    	},
    	async ({ id }) => {
    		const result = await client.getContact(id);
    		// Return minimal fields to reduce context size
    		const contact = toContactMinimal(result.data as unknown as Record<string, unknown>);
    		return {
    			content: [{ type: 'text', text: JSON.stringify(contact, null, 2) }],
    		};
    	},
    );
Behavior2/5

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

With no annotations, the description should disclose behavioral traits such as whether the operation is read-only, error handling on missing ID, or authentication requirements. The current text only implies reading without explicit guarantees.

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 unnecessary words. It is appropriately concise for a simple retrieval operation.

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?

The description is minimal but functional for a straightforward get-by-ID tool. However, given no output schema, it does not explain what 'contact details' includes, leaving some ambiguity for the agent.

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?

The schema already describes the 'id' parameter with 100% coverage. The description adds 'by ID' which echoes the schema but does not provide additional semantic context beyond what is already in the schema.

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 it retrieves contact details using an ID, distinguishing it from list or create operations. However, it does not specify what fields are returned or clarify the uniqueness of contacts.

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_contacts for multiple contacts. No prerequisites or context about when the ID is available.

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