Skip to main content
Glama

monitor_issue

Adds a specified user—or the authenticated user by default—as an observer on a MantisBT issue, so they receive updates and stay informed.

Instructions

Adds a user (or the authenticated user if omitted) as a monitor/observer of an issue.

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

Input Schema

NameRequiredDescriptionDefault
issue_idYes
usernameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the mutation intent and the default-target behavior (authenticated user when username is omitted), which is real behavioral value. However, it says nothing about idempotency when the user is already a monitor, whether adding another user requires elevated permissions, or what a successful/failed call looks like.

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?

A single sentence with the action verb front-loaded and zero filler; the optionality note is embedded in the exact place it matters. Nothing could be removed without losing information.

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

Completeness3/5

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

For a two-parameter mutation with no annotations and no output schema, the description covers intent and the key default but omits permission requirements, duplicate-monitor behavior, and error semantics. It is adequate to call the tool correctly in the happy path, but thin for a state-changing operation.

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 description coverage is 0%, so the description must compensate, and it does cover both parameters: issue_id is scoped to an issue and username is optional with the authenticated user as the default. It still does not clarify whether username is a login name versus display name or whether issue_id refers to a numeric internal ID, leaving format ambiguity.

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?

States a specific verb ('Adds') and a specific resource role ('as a monitor/observer of an issue'), which clearly separates it from sibling tools like add_issue_note or attach_issue_tags. It stops short of naming a sibling or contrasting the monitor action with any alternative, so differentiation is implied rather than explicit.

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 parenthetical '(or the authenticated user if omitted)' implies the self-monitoring case, which is a genuine usage cue for the optional parameter. There is no statement about when to use this versus other issue-mutation tools, nor any precondition such as needing visibility/permission on the issue.

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