Skip to main content
Glama
Sign In

Comma

by com.commareports
OverviewDiscussionsAdmin

delete_reviewer

Delete an agent-reviewer you own. Comments it already produced stay; their reviewer_id becomes null.

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": {
      "reviewer_id": "<reviewer_id>"
    },
    "name": "delete_reviewer"
  }
}

Input Schema

NameRequiredDescriptionDefault
reviewer_idYesUUID of the reviewer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 does disclose two important behaviors: the ownership requirement and the cascade effect on existing comments (reviewer_id set to null). It omits irreversibility confirmation and failure behavior for a non-owned or invalid reviewer_id, so it's strong but not complete.

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 tightly written sentences with zero filler; the destructive action and its data side effect are both front-loaded.

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 single-parameter delete with no output schema and no annotations, the description covers the key side effect and ownership gate. Missing a note on whether deletion is permanent/confirmed, but nothing critical is left for the agent to guess about the core operation.

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?

Schema description coverage is 100%, so the single reviewer_id parameter is already documented as a UUID. The description adds only the implicit constraint that the reviewer must be caller-owned, which is context rather than parameter syntax; baseline 3 applies.

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+resource ("Delete an agent-reviewer") and adds the ownership qualifier, which distinguishes it from create_reviewer/update_reviewer/list_reviewers. An agent can identify the operation without opening the schema.

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 "you own" phrasing implies the precondition, but there's no explicit when-to-use vs. alternatives guidance (e.g., update_reviewer for modification, list_reviewers for lookup) and no when-not-to-use or irreversibility warning. Usage is implied rather than stated.

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

All Comma toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources