Skip to main content
Glama

Compoid MCP

by com.compoid
OverviewDiscussionsAdmin

Compoid_delete_record

Delete a published Compoid record. IRREVERSIBLE.

The record is tombstoned and drops out of all search results. Use it to
clean up test records. Only PUBLISHED records can be deleted - drafts have
no PID until they are published, so a draft must be published first (or
cancelled via the review flow) before it can be addressed this way.

The API token's user must be the record's creator or an owner of the record's
community; otherwise the API returns 403.

Required:
    work_id: the record to delete - a published record PID (e.g.
        '4171t-rc787'), a full record URL
        (https://www.compoid.com/records/<pid>), or its OAI.

On success returns a confirmation (HTTP 204). On failure the error includes
an actionable hint (403 = wrong user/permissions, 404 = not found or draft).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
work_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior4/5

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

The description heavily discloses behavioral traits: it is destructive (tombstoned), affects search visibility, requires creator/owner permissions (403), and describes the success/failure responses including error hints. While annotations are absent, the description covers essential behavior well, though it could mention the tombstoned record's visibility in the API vs search results.

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?

Well-structured with introductory sentence, bullet-like sections for critical info, and a concise required parameter note. The formatting and emphasis on IRREVERSIBLE and limitations ensure the agent sees key points quickly without unnecessary verbosity.

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?

Given the tool's low complexity (single param), descriptive schema, and comprehensive behavioral coverage (permissions, error hints, irreversible nature), the description is complete and sufficient for accurate selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema only provides a name ('work_id') with 0% description coverage, the description fully explains the parameter: it accepts a PID, URL, or OAI, as shown with examples. This adds meaning beyond the schema and is precise.

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 clearly states it deletes a published Compoid recordholistically, using a specific verb ('Delete') and resource ('published Compoid record'). It includes the important nuance of being IRREVERSIBLE and that it applies to published records only, which differentiates it from update or create operations.

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 states when to use: 'clean up test records'. It also explains when not to use (for drafts: must be published first) and describes the alternative (cancelling via review flow). This is clear guidance on context and constraints.

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

All Compoid MCP 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