Skip to main content
Glama

pylon_get_issue

Retrieve a specific customer support issue by ID or issue number from the Pylon platform to access ticket details and status.

Instructions

Get a specific issue by ID or issue number

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe issue ID or issue number

Implementation Reference

  • MCP tool handler that takes an issue ID, calls PylonClient.getIssue, and returns the result as formatted JSON text content.
    async ({ id }) => {
    	const result = await client.getIssue(id);
    	return {
    		content: [{ type: 'text', text: JSON.stringify(result.data, null, 2) }],
    	};
    },
  • Zod input schema defining the required 'id' parameter as a string.
    {
    	id: z.string().describe('The issue ID or issue number'),
    },
  • src/index.ts:307-319 (registration)
    Registration of the 'pylon_get_issue' MCP tool with name, description, schema, and handler function.
    server.tool(
    	'pylon_get_issue',
    	'Get a specific issue by ID or issue number',
    	{
    		id: z.string().describe('The issue ID or issue number'),
    	},
    	async ({ id }) => {
    		const result = await client.getIssue(id);
    		return {
    			content: [{ type: 'text', text: JSON.stringify(result.data, null, 2) }],
    		};
    	},
    );
  • PylonClient helper method implementing the API call to GET /issues/{id} using the internal request method.
    async getIssue(id: string): Promise<SingleResponse<Issue>> {
    	return this.request<SingleResponse<Issue>>('GET', `/issues/${id}`);
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it's a 'Get' operation (implying read-only), but doesn't disclose behavioral traits like authentication needs, rate limits, error conditions, or what happens if the issue doesn't exist. The description is minimal and lacks crucial operational context.

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?

Extremely concise single sentence with zero waste. Every word earns its place: verb, resource, and key constraint. Front-loaded with the core purpose.

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?

For a read operation with no annotations and no output schema, the description is incomplete. It doesn't explain what information is returned, error handling, or operational constraints. Given the simplicity (1 parameter, 100% schema coverage), it's minimally adequate but leaves significant gaps in understanding the tool's behavior.

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 description coverage is 100%, with the single parameter 'id' documented as 'The issue ID or issue number'. The description adds no additional meaning beyond what's in the schema, simply restating 'by ID or issue number'. Baseline 3 is appropriate when schema does the heavy lifting.

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 issue', specifying it's by 'ID or issue number'. It distinguishes from siblings like pylon_list_issues (which lists multiple) and pylon_search_issues (which searches), but doesn't explicitly mention these alternatives in the description itself.

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_issues or pylon_search_issues. The description implies usage when you have a specific ID/number, but doesn't provide explicit context, prerequisites, or exclusions.

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