Skip to main content
Glama

Get issue models

get_issue_models
Read-only

Which models did, or are doing, an issue's work: each use with its 'model' (one id — 'opus-5.5' and 'claude-opus-5-5' are one), 'written' (as it was reported), 'name', 'vendor', 'via' (a router such as openmath, apart from the vendor), 'role' (plan, code, review…), 'source' — run (an agent run reported with report_agent_usage, bgs's included), agent (the tracker's own agents; 'built-in' is the tracker's own AI, named no further) or manual (set_issue_models) — 'agent', the dates and 'now' (begun and not ended). 'summary' gathers them by model. get_issue carries the summary as 'models'. Search: JQL model = "claude-opus-5-5" (or a vendor, or a router).

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": {
      "key": "<key>"
    },
    "name": "get_issue_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesIssue key, e.g. 'PM-1378'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description goes further by disclosing what the payload actually contains: the meaning of 'model' normalization ('opus-5.5' and 'claude-opus-5-5' are one), 'via' router separation from vendor, the four 'source' categories, and that 'now' means begun-and-not-ended. It does not cover pagination, ordering, or error behavior, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Information density is high and mostly front-loaded, but the single sentence is a run-on of quoted field names and nested parentheticals that is hard to parse on first read. The enumeration of every field name ('written', 'name', 'vendor', 'via', 'role', 'source') consumes space that behavioral context could have used.

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 no output schema, the description must carry the return shape, and it does so field by field, including the summary aggregation and how get_issue surfaces it. For a one-parameter read tool this is close to sufficient; only ordering, limits, and empty-state behavior are unaddressed.

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?

There is a single required 'key' parameter with 100% schema description coverage ('Issue key, e.g. PM-1378'), so the schema already does the work and per the rubric the baseline is 3. The description adds nothing about the key parameter itself; the JQL line describes a sibling search mechanism, not this parameter.

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?

The opening clause 'Which models did, or are doing, an issue's work' identifies the resource (model usage on an issue) and the retrieval intent, and the field list makes the return shape concrete. It falls short of a 5 because the verb is implied rather than stated and it never explicitly contrasts itself with get_agent_usage or list_models, which sit nearby.

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?

Guidance is present but indirect: 'get_issue carries the summary as models' tells the agent to use get_issue when only the summary is needed, and the JQL search line gives a second access path. There is no explicit statement of when this tool is preferred over get_agent_usage or list_models, so selection still requires inference.

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