Skip to main content
Glama
Sign In

Stride — AI software delivery platform

by page.stride
OverviewDiscussionsAdmin

Delete document

stride.delete_document
DestructiveIdempotent

Archive a Library document (meeting notes, PRD, spec, retro…). Removes it from the Library list and from stride.search_documents, but it stays RESTORABLE — a human can bring it back from the archived view. Idempotent on an already-archived document. Permanent purge is deliberately not available to agents.

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": {
      "documentId": "<documentId>"
    },
    "name": "stride.delete_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentIdYesThe document UUID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: the document is removed from the Library list and from stride.search_documents, it remains restorable by a human from an archived view, and the call is idempotent on an already-archived document. This resolves the tension between destructiveHint=true and the soft-delete semantics, which annotations alone could not convey.

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, front-loaded with the action and its real semantics, followed by side effects and the idempotency guarantee. Every sentence carries distinct information; nothing is repeated from the schema or annotations.

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 one-parameter mutation with no output schema, the description covers what is affected (Library listing and search index), reversibility, idempotency, and the unavailability of hard deletion. Nothing an agent needs in order to call it safely is missing.

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?

The schema documents the single documentId parameter at 100% coverage, so parameter meaning is already fully specified by the structured data. The description adds no further detail about the identifier format or resolution, which is acceptable at this coverage level but earns only the baseline.

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 ('Archive a Library document') and immediately clarifies that the name 'delete' actually means soft-archive, with examples of the document types covered. An agent can distinguish this from sibling delete_* tools and from update_document without opening a 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 clear context for use (removing a document from the Library and from search) and an explicit exclusion: permanent purge is not available to agents, so an agent should not look elsewhere for hard deletion. It does not point at sibling tools such as stride.restore_document or update_document as alternatives, which keeps it short of a 5.

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

All Stride — AI software delivery platform toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources