Skip to main content
Glama
com.woodstitch/tts-human-eval

com.woodstitch/tts-human-eval

Official

woodstitch_delete_file

Destructive

Delete an uploaded file from your account by file ID. Existing studies retain their copy, so removing the upload does not affect prior results.

Instructions

Delete one upload from your account by file id. Studies that already used the file keep their copy.

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": {
      "file_id": "<file_id>"
    },
    "name": "woodstitch_delete_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered by structured data. The description does add real value beyond that by explaining that studies which already used the file retain their copy, i.e. deletion is not cascading. It omits permission requirements and behavior when the id does not exist.

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

Conciseness4/5

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

Two short sentences with the operation and its scope front-loaded, followed by one non-obvious caveat. Nothing is padded, though the second sentence could be tied more explicitly to the deletion action.

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 single-parameter destructive tool with no output schema, the annotations supply the safety signals and the description adds the non-cascading guarantee. Only the provenance of file_id and not-found behavior are left unaddressed, which are minor gaps.

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

Parameters2/5

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

With one parameter and 0% schema description coverage, the description carries the full burden, but it only restates 'file id' without format, example, or where to obtain a valid id (presumably woodstitch_list_files). This is the weakest area of an otherwise competent definition.

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 one upload') plus the scoping unit ('one', 'by file id'), which clearly separates it from woodstitch_upload_files and woodstitch_list_files. An agent can identify the operation 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 Guidelines2/5

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

The description never says when to reach for this tool versus alternatives such as woodstitch_list_files (to find an id) or whether deletion is ever preferable to leaving a file in place. The second sentence explains a side effect of deleting, not when to delete.

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