Skip to main content
Glama

DeleteProperty

Remove specific properties from a RushDB graph database by providing the property ID to maintain clean data structures.

Instructions

Delete a property from the database

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
propertyIdYesID of the property to delete

Implementation Reference

  • The core handler function for the DeleteProperty tool, which deletes a property by its ID using the database utility.
    export async function DeleteProperty(params: { propertyId: string }) {
      const { propertyId } = params
    
      await db.properties.delete(propertyId)
    
      return {
        success: true,
        message: `Property '${propertyId}' deleted successfully`
      }
    }
  • tools.ts:413-421 (registration)
    Registration of the DeleteProperty tool in the central tools array, including its name, description, and input schema for MCP tool listing.
    {
      name: 'DeleteProperty',
      description: 'Delete a property from the database',
      inputSchema: {
        type: 'object',
        properties: { propertyId: { type: 'string', description: 'ID of the property to delete' } },
        required: ['propertyId']
      }
    },
  • Input schema definition for the DeleteProperty tool, specifying the required propertyId parameter.
    inputSchema: {
      type: 'object',
      properties: { propertyId: { type: 'string', description: 'ID of the property to delete' } },
      required: ['propertyId']
    }
  • Dispatch handler in the MCP server's CallToolRequestSchema handler that invokes the DeleteProperty tool.
    case 'DeleteProperty':
      const deletePropertyResult = await DeleteProperty({
        propertyId: args.propertyId as string
      })
      return {
        content: [
          {
            type: 'text',
            text: deletePropertyResult.message
          }
        ]
      }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Delete' implies a destructive mutation, the description doesn't specify whether this operation is reversible, what permissions are required, what happens to associated data, or what the response looks like. This is inadequate for a destructive tool with zero annotation coverage.

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, efficient sentence with zero wasted words. It's appropriately sized for a simple tool and front-loads the essential information.

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 that this is a destructive mutation tool with no annotations and no output schema, the description is incomplete. It lacks critical behavioral details (e.g., reversibility, permissions, side effects) and doesn't help differentiate it from sibling deletion tools, leaving significant gaps for agent understanding.

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%, with the single parameter 'propertyId' fully documented in the schema. The description doesn't add any meaning beyond what the schema provides (e.g., format examples, constraints, or edge cases), so it meets the baseline for high 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 clearly states the action ('Delete') and target resource ('a property from the database'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from sibling tools like DeleteRecord or DeleteRecordById, which also perform deletion operations on different resources.

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 provides no guidance on when to use this tool versus alternatives like DeleteRecord or DeleteRecordById. There's no mention of prerequisites, context, or exclusions, leaving the agent with insufficient information to choose between deletion tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rush-db/RushDB'

If you have feedback or need assistance with the MCP directory API, please join our Discord server