Skip to main content
Glama
Sign In
Neotoma

Neotoma

by markmhendrickson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

delete_entity

Hide an entity from current snapshots and queries through an immutable lifecycle observation. After the explicit authority cutover, serialized action sequence controls visibility; before cutover, existing legacy behavior applies.

Instructions

Hide an entity from current snapshots and queries through an immutable lifecycle observation. After the explicit authority cutover, serialized action sequence controls visibility; before cutover, existing legacy behavior applies. Each accepted request is a separate action, without an idempotency key or conditional rollback baseline. Physical legal erasure is a separate operation.

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": {
      "entity_id": "<entity_id>",
      "entity_type": "<entity_type>"
    },
    "name": "delete_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoOptional reason for deletion (audit)
user_idNoOptional. Inferred from authentication if omitted.
entity_idYesEntity ID to delete
entity_typeYesEntity type (e.g. company, person)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.15.0
  2. Removedv0.14.0
  3. Addedv0.12.1
  4. Removedv0.11.0
  5. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses several important traits: the operation is non-idempotent ('each accepted request is a separate action, without an idempotency key'), has no conditional rollback baseline, and behaves differently before vs. after an authority cutover. It also clarifies that physical erasure is separate. However, it omits key safety details like whether the hide is reversible (restore_entity exists) or what permissions are required.

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?

The description is front-loaded with the core purpose, and each sentence attempts to add distinct behavioral context. However, it is dense with unexplained jargon ('immutable lifecycle observation', 'explicit authority cutover') that reduces clarity, and the structure could be improved by separating operational guidance from behavioral notes.

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

Completeness3/5

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

For a mutation-style tool with no annotations or output schema, the description covers idempotency and lifecycle behavior but leaves critical gaps: it does not mention whether the operation is reversible, what happens to relationships on deletion, or authentication requirements. It is partially complete but insufficient for an agent to fully understand operational implications.

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 the input schema already documents all four parameters (including optional reason and user_id). The description adds no parameter-level meaning beyond what the schema provides, making 3 the baseline for full schema coverage.

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?

The description states a specific action ('Hide an entity from current snapshots and queries') and distinguishes it from physical legal erasure. However, it uses cryptic jargon like 'immutable lifecycle observation' and does not explicitly connect to sibling tools such as restore_entity, which would clarify reversibility. The core purpose is clear but muddied by phrasing.

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 explicit when-to-use guidance is provided. The description only implies this tool is for hiding rather than legal erasure, but it does not name alternatives (e.g., restore_entity, merge_entities, delete_relationship) or state conditions for choosing this tool over them. The routing context is largely absent.

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