Skip to main content
Glama
berthelius

Frihet MCP Server

Delete Client Note

delete_client_note
DestructiveIdempotent

Permanently delete a specific note from a client record. This action is irreversible, requiring confirmation to remove the note from the client's history.

Instructions

Permanently delete a note from a client. This action cannot be undone. / Elimina permanentemente una nota de un cliente. Esta accion no se puede deshacer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteIdYesNote ID / ID de la nota
clientIdYesClient ID / ID del cliente

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
successYes
Behavior4/5

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

The description explicitly states the action is irreversible ('This action cannot be undone'), which adds behavioral context beyond the annotations (destructiveHint: true, idempotentHint: true). No contradiction.

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 two sentences (bilingual), front-loaded with the action, and contains no unnecessary information.

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 simple deletion tool with two required parameters and an output schema (mentioned), the description adequately explains the action, irreversibility, and required context.

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 coverage is 100% with descriptions for each parameter. The description does not add parameter-level details, meeting the baseline expectation.

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 description clearly states 'Permanently delete a note from a client' with a strong verb and resource, and it distinguishes from siblings like create_client_note and list_client_notes.

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 when to use the tool (to permanently delete a note), but provides no explicit guidance on when not to use it or alternatives, which are available among sibling 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/berthelius/frihet-mcp'

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