Skip to main content
Glama

pylon_snooze_issue

Snooze a support issue until a specified time. Provide the issue ID and target time in RFC3339 format to postpone the issue.

Instructions

Snooze an issue until a specific time

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe issue ID
snooze_untilYesTime to snooze until in RFC3339 format

Implementation Reference

  • src/index.ts:926-939 (registration)
    Registration of the 'pylon_snooze_issue' tool with the MCP server. Defines the tool name, description 'Snooze an issue until a specific time', input schema (id and snooze_until as strings), and the handler that calls client.snoozeIssue.
    server.tool(
    	'pylon_snooze_issue',
    	'Snooze an issue until a specific time',
    	{
    		id: z.string().describe('The issue ID'),
    		snooze_until: z.string().describe('Time to snooze until in RFC3339 format'),
    	},
    	async ({ id, snooze_until }) => {
    		const result = await client.snoozeIssue(id, snooze_until);
    		return {
    			content: [{ type: 'text', text: JSON.stringify(result.data, null, 2) }],
    		};
    	},
    );
  • The handler function for pylon_snooze_issue. Receives id and snooze_until, calls client.snoozeIssue(id, snooze_until), and returns the issue data as formatted JSON.
    async ({ id, snooze_until }) => {
    	const result = await client.snoozeIssue(id, snooze_until);
    	return {
    		content: [{ type: 'text', text: JSON.stringify(result.data, null, 2) }],
    	};
    },
  • Input schema for pylon_snooze_issue: id (string) and snooze_until (string in RFC3339 format), both defined using Zod.
    {
    	id: z.string().describe('The issue ID'),
    	snooze_until: z.string().describe('Time to snooze until in RFC3339 format'),
    },
  • The snoozeIssue method on PylonClient. Sends a POST request to /issues/{id}/snooze with the snooze_until payload, returning a SingleResponse<Issue>.
    async snoozeIssue(
    	id: string,
    	snooze_until: string,
    ): Promise<SingleResponse<Issue>> {
    	return this.request<SingleResponse<Issue>>('POST', `/issues/${id}/snooze`, {
    		snooze_until,
    	});
    }
  • The SingleResponse<T> interface used as the return type for snoozeIssue, wrapping data (of type Issue) with a request_id.
    export interface SingleResponse<T> {
    	data: T;
    	request_id: string;
    }
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It only states the basic action without disclosing side effects (e.g., whether the issue's status changes, if it can be unsnoozed, or any permission requirements).

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 consists of a single, concise sentence that clearly conveys the tool's purpose with no superfluous words.

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 mutation tool with two parameters and no output schema, the description is adequate but lacks details on return value or reversibility. It is minimally sufficient.

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?

Both parameters ('id' and 'snooze_until') have descriptions in the schema. The description adds minimal extra meaning beyond confirming the temporal aspect. Schema coverage is 100%, 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?

The description 'Snooze an issue until a specific time' clearly states the action (snooze), resource (issue), and temporal constraint. It is distinct from sibling tools, none of which perform snoozing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no explicit guidance on when to use this tool versus alternatives like update_issue or delete_issue. Usage context is implied but not clarified.

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