Skip to main content
Glama
mohamed-ashraf-elsaed

loupe-mcp

by mohamed-ashraf-elsaed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_status

Move a comment through board stages: set In Progress when starting work, In Review when ready for human review. Only a person resolves a comment.

Instructions

Move a comment along the board. Set In Progress when you start it, and In Review when the change is ready for a human — only a person resolves a comment, so never set Resolved yourself.

Input Schema

NameRequiredDescriptionDefault
idYes
statusYesStage: queue / todo / in_progress / in_review / resolved. Legacy "open" and "done" are accepted too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.14.1
    • addedInput schema / properties / status / description
      Added value: +"Stage: queue / todo / in_progress / in_review / resolved. Legacy \"open\" and \"done\" are accepted too."
    • removedInput schema / properties / status / enum
      Removed value: -[
-  "open",
-  "in_progress",
-  "done"
-]
  2. First observedv0.5.2

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it discloses a critical policy constraint beyond the schema: the Resolved state is human-only. It does not cover idempotency, permission requirements, or failure behavior, but the most consequential behavioral gotcha is surfaced.

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 compact sentences, front-loaded with the action and then the per-status guidance. Every clause carries operational weight, including the trailing prohibition, with no filler.

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 simple two-parameter mutation with no output schema and no annotations, the description supplies the status semantics and the key restriction. It is slightly thin on what 'id' refers to and on the result of a successful move, but nothing essential to correct invocation 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 50% and the 'id' parameter is undocumented in the schema, but 'Move a comment along the board' implies id is the comment identifier. The description adds real meaning to the status parameter by mapping values to workflow intent (In Progress at start, In Review when ready for human, never Resolved), which goes beyond the schema's list of accepted strings.

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 description names a specific verb and resource: moving a comment's status along the board, which clearly distinguishes it from siblings like mark_thread_addressed or reply_to_companion. It does not explicitly name a sibling alternative, so it stops short of a 5, but an agent knows exactly what this tool mutates.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use guidance tied to workflow stages (In Progress when you start, In Review when ready for a human) plus a hard when-not rule (never set Resolved yourself, because only a person resolves). This is exactly the routing context an agent needs before invoking, with nothing left to inference.

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

Deploy Server

Other Tools