Skip to main content
Glama
Sign In
PM Context MCP Server

PM Context MCP Server

by jackhendon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_blockers_tool

Retrieve all blocked issues with their blocking reasons and assigned owners to identify and resolve blockers promptly.

Instructions

Get all issues currently flagged as blocked, including the blocking reason and the assignee responsible for resolving them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_blockers_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 the full burden. It clearly indicates a read operation ('Get') and specifies the returned data, but lacks details on scope (e.g., all projects vs. current user), pagination, or potential errors. It is minimally transparent but not overly detailed.

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 is a single, front-loaded sentence that directly communicates the tool's function and important output fields. Every word earns its place; no unnecessary information.

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?

With zero parameters and no output schema, the description adequately covers the query scope and return fields. The only minor gap is the lack of explicit scope boundaries (e.g., whether 'all' means globally or within a project), but this does not detract significantly from overall completeness for a simple tool.

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?

The tool has zero parameters, so the description does not need to explain parameter semantics. The baseline score of 4 applies since there are no parameters to describe.

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 uses a specific verb ('Get') and clearly identifies the resource ('all issues currently flagged as blocked') and key return fields (blocking reason, assignee). This clearly distinguishes it from sibling tools focused on sprints, own issues, or workload.

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 implies the tool is for retrieving blocked issues, which is a clear usage context. However, it does not explicitly mention when to use it versus sibling tools like search_issues_tool or get_my_issues_tool, nor does it state exclusions or conditions.

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