Skip to main content
Glama
Sign In

Tunc Orb

by com.tuncorb
OverviewDiscussionsAdmin

Delete Tunc Orb data

data_delete
Destructive

Remove Tunc Orb data when the user asks you to: one record, selected log entries, or a whole log. A delete cannot be undone. Use record for one ordinary record, entries for selected log entries, and log for an entire log. Supply the current revision from data_read, data_write or data_update; a stale revision is refused with revision_conflict, so reread and decide again. When you retry, send the same mutation_id so the delete applies once. This does not archive a shelf, delete a workspace or files, or delete by wildcard.

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": {
      "operation": "<operation>"
    },
    "name": "data_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoExact record or log name (UTF-8, at most 512 bytes, never normalized). Required for every operation. Collections are naming conventions such as contacts/<id>.
shelf_idNoShelf to use (a stable ID from data_read operation=shelves). Omit to use the current default shelf, which is resolved once and pinned for this call and its retries.
entry_idsNoentries only: exact entry IDs to delete (1-200).
operationYesrecord: one ordinary record. entries: selected entries of a log (entry_ids). log: an entire log. Every operation needs name and if_revision.
if_revisionNoCurrent revision from your latest read or write. Required for every operation. A stale revision is rejected with revision_conflict; reread and decide again.
mutation_idNoOptional: an ID you choose once for this delete (a UUID, or a mut_ ID from an earlier result) and send again when you retry, so the change never applies twice. Omit it and the service assigns one; the result carries it for data_read operation=status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the destructiveHint=true annotation, it discloses irreversibility ('A delete cannot be undone'), optimistic-concurrency behavior ('a stale revision is refused with revision_conflict, so reread and decide again'), and retry semantics via mutation_id. The idempotentHint=false annotation is not contradicted: deletes are only once-effective when the caller supplies mutation_id, which the description explains.

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?

Front-loads the destructive warning and operation routing, then conflict/retry handling, then scope exclusions. Every sentence carries distinct information an agent needs; there is no restatement of the tool name or filler.

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

Completeness5/5

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

For a destructive, non-idempotent tool with no output schema, the description covers irreversibility, required revision sourcing, conflict recovery, retry deduplication, and explicit out-of-scope actions. Nothing an agent needs to invoke it safely 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; the description adds an operation-to-parameter mapping and tells the agent where the if_revision value must come from (data_read/data_write/data_update) and how mutation_id enables safe retries. It does not add format details for name or shelf_id beyond what the schema already documents.

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 and resource ('Remove Tunc Orb data') and immediately enumerates the three supported scopes (one record, selected log entries, a whole log). It also names the sibling tools (data_read, data_write, data_update) that supply the required revision, so an agent can place it in the toolset without opening schemas.

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?

Explicitly says when to use it ('when the user asks you to'), maps each operation to its case ('record for one ordinary record, entries for selected log entries, log for an entire log'), and names exclusions ('does not archive a shelf, delete a workspace or files, or delete by wildcard'). This is the full when/when-not/alternative pattern.

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

All Tunc Orb 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