Skip to main content
Glama
Sign In
AIMFP

AIMFP

by aryanduntley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_settings_entry

Destructive

Remove a record from a user preferences table by specifying the table name and record ID.

Instructions

Delete entry from user_preferences.db table

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": {
      "table": "<table>",
      "record_id": "<record_id>"
    },
    "name": "delete_settings_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableYesTable name in user_preferences.db
record_idYesRecord ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.37.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description echoes the deletion behavior but adds no additional context (e.g., cascade effects, permanence). With annotations present, the minimal description is adequate.

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?

Single sentence of 5 words is extremely concise and front-loaded, containing only the essential information without any fluff.

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?

Given simple parameters and no output schema, the description is minimally complete. However, it lacks information about validation (e.g., whether the table/record must exist) and permanence of the deletion.

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 fully documents both parameters (table and record_id). The description adds no extra semantic information beyond what the input schema provides.

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?

Description states 'Delete entry from user_preferences.db table', which clearly identifies the action (delete) and resource (settings entry). It distinguishes from sibling tools like add_settings_entry and update_settings_entry.

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

Usage Guidelines3/5

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

The description implies use for deleting settings entries but provides no explicit guidance on when to use this tool versus other delete tools (e.g., delete_project_entry) or any prerequisites.

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