Skip to main content
Glama

pylon_get_team

Retrieve team details by ID from the Pylon customer support platform to manage team information and access specific data.

Instructions

Get a specific team by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe team ID

Implementation Reference

  • src/index.ts:600-612 (registration)
    Registration of the 'pylon_get_team' MCP tool. Includes input schema (id: z.string()), description, and inline handler function that calls PylonClient.getTeam(id) and returns the result as formatted JSON text content.
    server.tool(
    	'pylon_get_team',
    	'Get a specific team by ID',
    	{
    		id: z.string().describe('The team ID'),
    	},
    	async ({ id }) => {
    		const result = await client.getTeam(id);
    		return {
    			content: [{ type: 'text', text: JSON.stringify(result.data, null, 2) }],
    		};
    	},
    );
  • Core handler logic in PylonClient: performs HTTP GET request to `/teams/${id}` endpoint via the private request method to fetch team data.
    async getTeam(id: string): Promise<SingleResponse<Team>> {
    	return this.request<SingleResponse<Team>>('GET', `/teams/${id}`);
    }
  • TypeScript interface defining the structure of a Team object returned by the Pylon API.
    export interface Team {
    	id: string;
    	name: string;
    	users: { email: string; id: string }[];
    }
  • Private HTTP request utility method used by getTeam to make authenticated API calls to Pylon.
    private async request<T>(
    	method: string,
    	path: string,
    	body?: object,
    ): Promise<T> {
    	const url = `${PYLON_API_BASE}${path}`;
    	const headers: Record<string, string> = {
    		Authorization: `Bearer ${this.apiToken}`,
    		'Content-Type': 'application/json',
    		Accept: 'application/json',
    	};
    
    	const response = await fetch(url, {
    		method,
    		headers,
    		body: body ? JSON.stringify(body) : undefined,
    	});
    
    	if (!response.ok) {
    		const errorText = await response.text();
    		throw new Error(
    			`Pylon API error: ${response.status} ${response.statusText} - ${errorText}`,
    		);
    	}
    
    	return response.json() as Promise<T>;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves a team but doesn't describe what information is returned, whether it requires authentication, if it's idempotent, or how it handles errors (e.g., invalid IDs). For a read operation with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 with zero wasted words. It is appropriately sized for a simple retrieval tool and front-loaded with the essential information.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what data is returned (e.g., team details), potential errors, or authentication requirements. For a tool that likely returns structured team information, this omission makes it inadequate for full contextual understanding.

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 description coverage is 100%, with the parameter 'id' documented as 'The team ID'. The description adds no additional meaning beyond what the schema provides, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 ('a specific team by ID'), making the purpose unambiguous. It distinguishes this tool from list operations like 'pylon_list_teams' by specifying retrieval of a single team. However, it doesn't explicitly differentiate from other 'get' tools like 'pylon_get_account' beyond the resource name.

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., needing a team ID), contrast with 'pylon_list_teams' for browsing teams, or specify error conditions (e.g., what happens if the ID doesn't exist). Usage is implied but not explicitly stated.

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