Skip to main content
Glama
Sign In

Ripey

by app.ripey
OverviewDiscussionsAdmin

Delete a draft

delete_draft
DestructiveIdempotent

Delete an unpublished draft the user doesn't want. Published products can't be deleted this way. Pass the store's agent_key (returned by open_store).

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": {
      "agent_key": "<agent_key>",
      "product_id": "<product_id>"
    },
    "name": "delete_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_keyYesThe store's agent key (rpy_…), returned by open_store
product_idYesDraft id from create_product, e.g. p_1a2b3c

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds a real behavioral precondition beyond those flags: only unpublished drafts are eligible, which prevents a failed or wrongly-scoped call.

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?

Three short sentences: operation, exclusion, and credential requirement, in that order. Nothing is redundant and the critical restriction is 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 simple two-parameter destructive mutation, the definition covers purpose, eligibility, and prerequisites, and the annotations carry the destructive/idempotent semantics. Only the post-deletion outcome is unstated, which is minor given there is no output schema.

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 both parameters are already fully documented, including the agent_key's origin. The description's note about agent_key merely restates the schema, adding no new meaning.

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 ('Delete an unpublished draft') with a scope qualifier that separates it from create_product, publish, and list_products. An agent can identify the operation and its target 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 Guidelines4/5

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

Gives a clear when-to-use signal ('the user doesn't want') and a when-not rule ('Published products can't be deleted this way'). It stops short of naming what to do instead for published items, leaving that to inference.

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

All Ripey 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