Skip to main content
Glama

Set issue models

set_issue_models
Destructive

Say by hand which models did an issue's work, each with its part — the same list the issue's «Models» block edits. The list REPLACES the models set by hand before (an empty list clears them); models that agent runs and the tracker's agents brought stay, and a run reports its own with report_agent_usage ('model' / 'models'). Name a model as you know it: 'opus-5.5', 'claude-opus-5-5', 'deepseek/deepseek-v4.1-flash' — known names are read as one id, any other is kept as written; 'via' is a router such as 'openmath'. 'role': plan, code, review, test, research, or another short word. At most 20. Requires permission to edit the issue. Answers with the issue's models as get_issue_models does.

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>",
      "models": "<models>"
    },
    "name": "set_issue_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesIssue key, e.g. 'PM-1378'.
modelsYesThe models set by hand, the whole list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

The description adds critical behavior beyond the destructiveHint annotation: the new list REPLACES prior manually set models, an empty list clears them, and agent-run/tracker-agent models remain untouched. It also states the 20-model limit and the edit-permission requirement.

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 dense but front-loaded, covering purpose, replacement semantics, naming behavior, role values, limits, permissions, and return shape without wasting sentences. Every clause contributes an operational constraint.

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?

For a destructive mutation with no output schema, the description covers what gets replaced, what is preserved, permissions, constraints, and the return shape by reference to get_issue_models. An agent has enough information to invoke it correctly.

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 100%, so the baseline is 3. The description adds useful semantics such as the hard limit of 20 models and the normalization rule that known names are read as one id while unknown names are kept as written.

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 a specific verb and resource: manually recording which models did an issue's work, matching the issue's «Models» block. It also distinguishes this from related behavior by noting that agent-run models are reported via report_agent_usage instead.

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?

It clearly establishes the manual-use context and explains that agent runs use report_agent_usage instead. However, it does not explicitly name get_issue_models as the read-only alternative for inspecting the current list.

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