Skip to main content
Glama
Sign In
Pylon MCP Server

Pylon MCP Server

by mgmonteleone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

pylon_find_similar_issues_for_requestor

Identify recurring issues by finding problems reported by the same requestor as the source issue.

Instructions

Find issues from the same requestor as the source issue to identify recurring patterns.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "issue_id": "<issue_id>"
    },
    "name": "pylon_find_similar_issues_for_requestor"
  }
}

Input Schema

NameRequiredDescriptionDefault
issue_idYesPylon issue ID
queryNoOptional search terms; defaults to source issue title
limitNoMax results to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.7.2

TDQS

A3.7/5.0
Behavior3/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 describes a read/search operation but does not disclose behavioral traits such as rate limits, authentication requirements, or what happens with no results.

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?

Single sentence that is concise and front-loaded with the key action and resource.

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 does not mention the return format or pagination behavior, and there is no output schema to compensate. While the tool is simple, additional context would improve completeness.

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 description does not add any meaning beyond the schema. The schema already provides adequate descriptions for each parameter, 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 clearly states it finds issues from the same requestor as the source issue, which differentiates it from sibling tools like pylon_find_similar_issues_for_account (by account) and pylon_find_similar_issues_global (global search).

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 phrase 'to identify recurring patterns' implies a use case, but there is no explicit guidance on when to use this tool versus the similar siblings, or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools