fiken-mcp

fiken_delete_contact

Destructive

Delete a contact from Fiken, or automatically mark it as inactive if associated records exist.

Instructions

Deletes a contact, or marks it inactive if it has associated records

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": {
      "contactId": "<contactId>"
    },
    "name": "fiken_delete_contact"
  }
}

Input Schema

Name	Required	Description	Default
`contactId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jul 30, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true. The description adds valuable context: the conditional behavior of marking inactive instead of deleting when there are associated records. This is beyond the annotation, though it could mention permissions or reversibility.

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, front-loaded sentence with no unnecessary words. It efficiently conveys the core action and condition.

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

Completeness4/5

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

For a simple 1-param tool with no output schema, the description covers the essential action and condition. Minor gaps: no mention of return value or whether the contact can be reactivated, but overall adequate.

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

Parameters1/5

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

With 0% schema description coverage, the description must explain the 'contactId' parameter, but it does not. The param meaning is left entirely to the agent to infer from the tool name and schema.

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 the tool deletes a contact or marks it inactive if it has associated records. This is a specific verb-resource combination and distinguishes it from sibling tools like fiken_update_contact or fiken_list_contacts.

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 usage for deleting or inactivating contacts but does not explicitly state when to use this tool over alternatives (e.g., updating the contact's status via fiken_update_contact). No when-not or alternatives are mentioned.

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

Deploy Server