Skip to main content
Glama

pylon_get_team

Retrieve a specific team's details using its unique ID. Access team information from the Pylon customer support platform.

Instructions

Get a specific team by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe team ID

Implementation Reference

  • The MCP tool handler for 'pylon_get_team'. It registers a server.tool with the name 'pylon_get_team' and description 'Get a specific team by ID'. It takes an 'id' string input, calls client.getTeam(id), and returns the team data as JSON.
    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) }],
    		};
    	},
    );
  • Input schema for the tool: a 'z.string()' parameter named 'id' described as 'The team ID'.
    {
    	id: z.string().describe('The team ID'),
    },
  • src/index.ts:1167-1167 (registration)
    Registration of the tool via server.tool() call with name 'pylon_get_team'.
    server.tool(
  • The PylonClient.getTeam() method that executes the actual HTTP GET request to /teams/{id} endpoint. It's called by the handler.
    async getTeam(id: string): Promise<SingleResponse<Team>> {
    	return this.request<SingleResponse<Team>>('GET', `/teams/${id}`);
    }
  • The Team interface defining the shape of the returned team object (id, name, users array).
    export interface Team {
    	id: string;
    	name: string;
    	users: { email: string; id: string }[];
    }
Behavior2/5

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

No annotations provided, and the description only implies a read operation. Missing details on error handling, auth requirements, or behavior when ID is invalid.

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?

Exceptionally concise (5 words) with no wasted text. Every word is necessary 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?

For a simple tool with one parameter and no output schema, the description provides basic purpose but omits details about return value or error scenarios. Adequate but not complete.

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 covers the parameter with description 'The team ID' (100% coverage). The description adds no additional meaning beyond the schema, earning baseline of 3.

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?

The description clearly states the action (Get) and resource (team) with the identifier (by ID), distinguishing it from sibling tools like pylon_list_teams or pylon_create_team.

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_teams or pylon_search_teams. Does not mention prerequisites or context.

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