Skip to main content
Glama

Update issue status

update-issue-status
Destructive

Mark a site health issue done or reopen it. The status applies to the issue on that domain, identified by its fingerprint, across audits. issue_fingerprint comes from get-audit-issues.

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": {
      "domain_id": "<domain_id>",
      "issue_fingerprint": "<issue_fingerprint>",
      "status": "<status>"
    },
    "name": "update-issue-status"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYesNew status
domain_idYesDomain ID from list-domains
issue_fingerprintYesissue_fingerprint from get-audit-issues

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / domain_id / description
      Previous value: -"Domain ID"New value: +"Domain ID from list-domains"
    • changedInput schema / properties / issue_fingerprint / description
      Previous value: -"64-char hex issue fingerprint"New value: +"issue_fingerprint from get-audit-issues"
  2. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / domain_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Adds real context beyond the annotations: the change applies at the domain+fingerprint level and persists across audits, which is not obvious from the schema. "Reopen it" implies the operation is reversible, which usefully softens the destructiveHint=true flag without contradicting it. Doesn't cover permission requirements or what is returned on success.

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?

Three short sentences, front-loaded with the action and followed by the scoping rule and the parameter provenance. Nothing is redundant with the name or 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?

No output schema exists, but the tool is a simple three-required-param mutation whose effect and identity model are fully explained. Minor gaps remain around success behavior and whether an already-done issue is a no-op, but nothing an agent needs in order to invoke it correctly is missing.

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, but the description adds interpretive value the schema lacks — that domain_id plus issue_fingerprint together scope the issue, and that the fingerprint is stable across audits. It also anchors issue_fingerprint's provenance to a sibling tool, reinforcing the schema's own note.

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?

States a specific verb pair and resource ("Mark a site health issue done or reopen it") and explains the exact identity model — the issue on that domain, keyed by fingerprint, across audits. An agent can distinguish this from read-only siblings like get-audit-issues or get-site-health-summary immediately.

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?

Gives clear context for use (setting an issue to done, or reopening) and names the prerequisite source for issue_fingerprint via get-audit-issues. It stops short of explicit when-not guidance or naming alternatives for bulk status changes, so it is clear but not exclusive.

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