Skip to main content
Glama

get_issue

Retrieve the full history of a specific issue by its ID to get detailed context without loading the entire project summary.

Instructions

Read one specific issue's full history by ID (token-efficient).

Use this when you only need one issue's context instead of the whole
summary. Example: get_issue('0042').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issue_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The tool handler for 'get_issue'. Decorated with @mcp.tool() and @safe_tool. Reads one specific issue's full history by ID by globbing for '{issue_id}-*.md' in the issues directory and returning the file contents.
    @mcp.tool()
    @safe_tool
    def get_issue(issue_id: str) -> str:
        """Read one specific issue's full history by ID (token-efficient).
    
        Use this when you only need one issue's context instead of the whole
        summary. Example: get_issue('0042')."""
        from projectmem.storage import issues_dir
        idir = issues_dir()
        matches = list(idir.glob(f"{issue_id}-*.md"))
        if not matches:
            return f"No issue found with ID {issue_id}."
        return matches[0].read_text(encoding="utf-8")
  • Registration via the @mcp.tool() decorator, which registers the function as an MCP tool on the FastMCP server instance.
    @mcp.tool()
  • The docstring serves as the schema/description for the tool. It describes the tool's purpose and provides an example usage (get_issue('0042')). The parameter 'issue_id: str' is the input schema.
    """Read one specific issue's full history by ID (token-efficient).
    
    Use this when you only need one issue's context instead of the whole
    summary. Example: get_issue('0042')."""
  • The issues_dir() helper function used by get_issue. It returns the path to the .projectmem/issues/ directory, calling require_mem_dir() to find the project root.
    def issues_dir(root: Path | None = None) -> Path:
        return require_mem_dir(root) / ISSUES_DIR
  • The ISSUES_DIR constant defining the issues subdirectory name as 'issues'.
    ISSUES_DIR = "issues"
Behavior4/5

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

No annotations provided, but description indicates read-only operation and mentions 'token-efficient', adding useful behavioral insight.

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 with two sentences and an example, front-loaded with purpose, no wasted words.

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

Completeness5/5

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

Given the tool's simplicity (one parameter, output schema exists), the description is fully adequate, covering purpose and usage.

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 has 0% coverage, but description provides an example usage ('get_issue('0042')') which partially compensates by illustrating the parameter format.

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 reads a specific issue's full history by ID, and distinguishes from siblings like get_summary by emphasizing single-issue context.

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

Usage Guidelines4/5

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

Explicitly tells when to use this tool (when needing one issue's context instead of the whole summary), providing clear usage context.

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/riponcm/projectmem'

If you have feedback or need assistance with the MCP directory API, please join our Discord server