Skip to main content
Glama
Sign In
Ryft MCP

Ryft MCP

by bkawk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

disputes.deleteEvidence

Remove evidence from a Ryft dispute to manage case details by deleting text entries or files associated with a specific dispute ID.

Instructions

Delete evidence from a Ryft dispute.

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": {
      "id": "<id>"
    },
    "name": "disputes.deleteEvidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
textNo
filesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. Fails to disclose whether deletion is reversible, if it affects dispute status, or timing restrictions (e.g., only deletable before challenge submitted).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence of 6 words is appropriately front-loaded, but given the complexity (destructive operation, 3 undocumented parameters), this brevity constitutes underspecification rather than optimal conciseness.

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

Completeness2/5

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

Destructive operation with 3 parameters, zero schema descriptions, no annotations, and no output schema requires substantial documentation. The 6-word description is inadequate for safe and correct invocation.

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

Parameters1/5

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

Schema has 0% description coverage. Description fails to explain what the 'id', 'text', and 'files' parameters represent (e.g., are 'text' and 'files' evidence IDs or content? Is 'id' the dispute ID?). No compensation for undocumented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States specific verb 'Delete' and resource 'evidence from a Ryft dispute'. Distinguishes from sibling 'disputes.addEvidence' through inverse action, though does not explicitly name the sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

Provides no guidance on when to use this tool versus disputes.addEvidence, disputes.accept, or disputes.challenge. No mention of prerequisites (e.g., dispute state requirements) or workflow constraints.

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

Deploy Server

Other Tools