Skip to main content
Glama
Sign In
Sourcebook

Sourcebook

by mecoskun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

delete_document

Remove a single indexed document by ID, or clear all documents from the Sourcebook workspace when no ID is provided.

Instructions

Delete one document, or all documents in this workspace when no ID is provided.

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": {
      "session_id": "<session_id>"
    },
    "name": "delete_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYes
document_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It usefully reveals the dangerous default that omitting document_id deletes all documents in the workspace. However, it does not mention irreversibility, permission requirements, or what happens after deletion, which are important for a destructive operation.

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?

The description is a single, front-loaded sentence with no filler. It efficiently conveys the core action and the critical all-documents branch without redundancy.

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?

Given this is a destructive tool with no annotations and no output schema, the description is not complete enough for safe invocation. It warns about the all-documents case but omits session_id semantics, postconditions, and any safety or error context.

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?

Schema description coverage is 0%, so the description must compensate. It explains document_id semantics well: present means one document, absent means all documents. But it does not explain the required session_id parameter at all, leaving half the parameters unexplained despite the low schema coverage.

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 names the action ('Delete') and the resource ('document'), and distinguishes two modes: deleting one document or all documents in the workspace when no ID is provided. This makes its purpose distinct from siblings like index_document, list_documents, and search_documents.

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?

The description gives explicit usage guidance for both parameter cases: provide a document_id to delete a single document, omit it to delete all documents in the workspace. It does not name alternatives or exclusion conditions, but no sibling is a deletion tool, so the context is reasonably clear.

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