Skip to main content
Glama
Sign In
AIMFP

AIMFP

by aryanduntley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_interaction

Destructive

Delete an interaction by its ID, providing a reason, severity, source, and type for the deletion.

Instructions

Delete interaction

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": {
      "interaction_id": "<interaction_id>",
      "note_reason": "<note_reason>",
      "note_severity": "<note_severity>",
      "note_source": "<note_source>",
      "note_type": "<note_type>"
    },
    "name": "delete_interaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
interaction_idYesInteraction ID to delete
note_reasonYesDeletion reason
note_severityYes'info', 'warning', 'error'
note_sourceYes'ai' or 'user'
note_typeYes'entry_deletion'entry_deletion

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.37.0

TDQS

D1.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, so the description's 'Delete interaction' adds no new behavioral context. There is no mention of cascading deletes, reversibility, permissions, or side effects beyond the deletion itself.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While very concise (2 words), the description is under-specified and fails to provide essential information. Structure is non-existent. Conciseness without utility is not beneficial.

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

Completeness1/5

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

Given the tool's destructive nature (destructiveHint=true) and 5 required parameters, the description is severely lacking. It does not explain what an interaction is, what the consequences of deletion are, or how to appropriately use the note parameters. No output schema means more burden on description, which it fails to meet.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with clear descriptions for all 5 parameters. The description 'Delete interaction' adds no additional meaning to any parameter. Baseline is 3 for high coverage, but the description contributes no value, resulting in a 2.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Delete interaction' is a tautology of the tool name 'delete_interaction'. It does not differentiate what an 'interaction' is from other deletable entities like files, flows, or tasks. Among many sibling delete tools, no distinction is provided.

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?

No usage guidance is given. There is no indication of when to use this tool instead of alternatives, no prerequisites (e.g., needing an interaction ID from a get function), and no warnings about consequences. Sibling tools like get_interactions_by_file could provide context but are not referenced.

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