Skip to main content
Glama
Sign In

mcp-server

by me.ceki
OverviewDiscussionsAdmin

Delete Correction

delete-correction

[Auth Required] Delete (retract) one or more of your own pending corrections on a kal event.

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": {
      "event_id": "<event_id>",
      "ids": "<ids>"
    },
    "name": "delete-correction"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesCorrection IDs to delete (your own pending corrections only)
event_idYesEvent ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It adds an auth requirement and states the ownership/pending restriction, which is useful, but it does not mention side effects, irreversibility, errors, or behavior when corrections are not pending or owned by another user.

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 front-loads the auth requirement and then states the precise action and target. There is no filler or redundant phrasing.

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 delete operation with no output schema or nested objects, the description plus schema provides enough information for an agent to invoke it correctly. It lacks only optional details about side effects or return values, which are minor for this scope.

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 parameters are already documented in the schema. The description adds no extra parameter-level meaning beyond the schema, so it meets the baseline without adding further value.

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 action ('Delete (retract)') and a specific resource ('one or more of your own pending corrections on a kal event'). This clearly distinguishes the tool from related siblings such as vote-correction.

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?

The description makes the usage context clear: the tool is for retracting the caller's own pending corrections, and it notes that authentication is required. It does not explicitly mention when NOT to use it or compare it to alternatives, but the scope is sufficiently clear for selection.

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

All mcp-server 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