Skip to main content
Glama

Delete Fact Definition

lexq_facts_delete
Destructive

Delete a fact definition. System facts cannot be deleted. Neither can a fact that any rule references: that call fails with FD-006 and reports the count. Rules in deleted groups do not count. Remove the references first.

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": {
      "factId": "<factId>"
    },
    "name": "lexq_facts_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
factIdYesFact definition ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations' destructive operation signal, the description discloses referential-integrity blocking, the FD-006 failure code, the reported reference count, and the deleted-group exception. These are substantial failure and scope details that help an agent predict and handle the call's behavior.

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 front-loaded with the operation and uses short sentences for the restrictions, error behavior, exception, and remedy. Every sentence earns its place, with no filler or repetition of structured parameter details.

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

Completeness5/5

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

For a destructive tool with one required parameter, it covers the resource, deletion blockers, precise failure behavior, an important exception, and the corrective action. Together with the complete parameter schema and destructive annotations, this is sufficient for correct selection and invocation.

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?

The schema fully documents the sole factId parameter, including its purpose and UUID constraints. The description adds no further parameter meaning, so the high schema coverage supports the baseline score of 3.

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 opening sentence states the exact operation and resource: deleting a fact definition. This clearly distinguishes the tool from fact creation, update, and listing siblings, as well as from the rule and group deletion tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-not conditions: system facts and facts referenced by applicable rules cannot be deleted. "Remove the references first" supplies the prerequisite remediation, while the deleted-group exception clarifies which references matter.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.