Skip to main content
Glama

delete_relation

Remove specific entity relations by specifying source, target, and relation type, enhancing data management on the libSQL-based server.

Instructions

Delete a specific relation between entities

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYesSource entity name
targetYesTarget entity name
typeYesType of relation

Implementation Reference

  • The handler function that implements the core logic of the 'delete_relation' MCP tool. It calls the database delete_relation method and formats the success or error response.
    async ({ source, target, type }) => {
    	try {
    		await db.delete_relation(source, target, type);
    		return {
    			content: [
    				{
    					type: 'text' as const,
    					text: `Successfully deleted relation: ${source} -> ${target} (${type})`,
    				},
    			],
    		};
    	} catch (error) {
    		return {
    			content: [
    				{
    					type: 'text' as const,
    					text: JSON.stringify(
    						{
    							error: 'internal_error',
    							message:
    								error instanceof Error
    									? error.message
    									: 'Unknown error',
    						},
    						null,
    						2,
    					),
    				},
    			],
    			isError: true,
    		};
    	}
    },
  • Valibot schema defining the input parameters for the delete_relation tool: source, target, and type as strings.
    const DeleteRelationSchema = v.object({
    	source: v.string(),
    	target: v.string(),
    	type: v.string(),
    });
  • src/index.ts:277-282 (registration)
    Registration of the 'delete_relation' tool on the MCP server, specifying name, description, and schema.
    server.tool<typeof DeleteRelationSchema>(
    	{
    		name: 'delete_relation',
    		description: 'Delete a specific relation between entities',
    		schema: DeleteRelationSchema,
    	},
  • Database helper method that performs the actual SQL DELETE operation for a specific relation and handles errors.
    async delete_relation(
    	source: string,
    	target: string,
    	type: string,
    ): Promise<void> {
    	try {
    		const result = await this.client.execute({
    			sql: 'DELETE FROM relations WHERE source = ? AND target = ? AND relation_type = ?',
    			args: [source, target, type],
    		});
    
    		if (result.rowsAffected === 0) {
    			throw new Error(
    				`Relation not found: ${source} -> ${target} (${type})`,
    			);
    		}
    	} catch (error) {
    		throw new Error(
    			`Failed to delete relation: ${
    				error instanceof Error ? error.message : String(error)
    			}`,
    		);
    	}
    }
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. It states 'Delete', implying a destructive mutation, but doesn't disclose behavioral traits such as whether deletion is permanent, requires specific permissions, has side effects (e.g., cascading deletions), or what happens on success/failure. This is a significant gap for a mutation 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 waste. It's appropriately sized and front-loaded, clearly stating the core action without unnecessary elaboration, making it easy to parse quickly.

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 the complexity of a destructive operation with no annotations and no output schema, the description is incomplete. It lacks crucial context like what 'delete' entails (e.g., irreversible), expected outcomes, error handling, or how it differs from sibling tools. For a mutation tool, this minimal description is inadequate.

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 schema already documents all three parameters (source, target, type) with basic descriptions. The description adds no additional meaning beyond what the schema provides, such as examples of relation types or how entities are identified. Baseline 3 is appropriate when the schema does the heavy lifting.

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 the resource ('a specific relation between entities'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'delete_entity' or 'create_relations', which would require specifying what makes this tool unique for relation deletion versus entity deletion or relation creation.

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. With siblings like 'delete_entity' and 'create_relations', it's unclear if this is for removing existing relations only, or if there are prerequisites (e.g., the relation must exist). No explicit when/when-not or alternative tools are mentioned.

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

Related 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/spences10/mcp-memory-libsql'

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