Skip to main content
Glama
Sign In
PM Context MCP Server

PM Context MCP Server

by jackhendon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_my_issues_tool

Retrieve all issues assigned to a specific team member, sorted by priority, using their full name.

Instructions

Get all issues assigned to a team member, sorted by priority. Use the person's full name (e.g. 'Priya Sharma').

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": {
      "assignee_name": "<assignee_name>"
    },
    "name": "get_my_issues_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
assignee_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description adds the behavioral trait 'sorted by priority', but does not disclose other relevant details such as permissions, empty result behavior, or whether the list is exhaustive. A moderate score is appropriate.

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?

Two concise, front-loaded sentences. Every phrase earns its place, with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-parameter tool with no output schema, the description covers the core behavior and parameter usage adequately. It lacks alternative guidance, but that is captured in the usage guidelines dimension.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description compensates by specifying the parameter format ('full name') and giving an example ('Priya Sharma'), adding meaning beyond the bare schema field 'assignee_name'.

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 states 'Get all issues assigned to a team member, sorted by priority' with a specific verb and resource, clearly distinguishing this from siblings like search_issues_tool and get_team_workload_tool.

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?

Provides no guidance on when to use this tool versus alternatives. The only usage instruction ('Use the person's full name') addresses parameter format, not tool selection.

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