Skip to main content
Glama

Get an issue's history

get_issue_activity
Read-only

What people and Fictura did to one issue, newest first: status changes, assignments, priority, notes with their text, tickets, regressions. Use it before changing an issue, to see who already looked at it.

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": "get_issue_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows (default 25)
cursorNonext_cursor from the last answer
issue_idYesIssue id, from list_error_issues

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: explicit newest-first ordering and the disclosure that note text is included, hinting at user-written content. It says nothing about volume, pagination behavior, or how far back history is retained, which matters for an audit-style feed.

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 sentences, both earning their place: the payload/ordering comes first, the usage trigger second. No filler, no restatement of the title.

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 read-only, three-parameter tool with a fully described schema and no output schema, the definition covers what the agent needs to decide and call it. The only meaningful omission is any hint about pagination depth or history window, which the schema touches only structurally via cursor.

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 coverage is 100%, with issue_id, limit and cursor all documented in the schema itself, so the baseline of 3 applies. The description only reinforces single-issue scoping ("one issue") and adds no format or semantics for limit or cursor beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"What people and Fictura did to one issue" gives a specific verb-plus-resource, and the enumerated event types (status changes, assignments, priority, notes, tickets, regressions) make it plainly a history feed rather than the current issue state. It stops short of naming a sibling like get_error_issue as the alternative, so it does not fully differentiate by contrast.

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?

"Use it before changing an issue, to see who already looked at it" is an explicit, actionable when-to-use trigger tied to a real workflow. There is no when-not guidance and no named alternative for agents who want current state instead of history.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources