Skip to main content
Glama
Sign In
astra-knowledge-base-mcp

astra-knowledge-base-mcp

by alrcatraz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

kb_delete_chunk

Removes a specific chunk from a knowledge base by providing its chunk ID. Use this to delete unwanted content entries.

Instructions

Delete a single chunk by ID

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": {
      "kb": "<kb>",
      "chunk_id": "<chunk_id>"
    },
    "name": "kb_delete_chunk"
  }
}

Input Schema

NameRequiredDescriptionDefault
kbYesKnowledge base name
chunk_idYesChunk ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, and the description only states the action. It fails to disclose important behavioral traits such as irreversibility, permission requirements, side effects, or return value.

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 concise sentence. Every word is necessary and front-loaded with the core action and resource.

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?

For a delete operation with no output schema, the description lacks crucial context such as error handling, success/failure indicators, or whether deletion is permanent. More detail is needed for safe use.

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 each parameter is already documented. The description only reinforces 'by ID' for chunk_id, adding minimal meaning beyond the schema.

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 states the action (delete), resource (a single chunk), and method (by ID). It distinguishes from sibling tools like 'kb_delete' which likely targets entire knowledge bases.

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?

No guidance on when to use this tool over alternatives. The description does not contrast with 'kb_delete' or other chunk-related tools, leaving the agent to infer usage from naming alone.

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