Skip to main content
Glama
Sign In
Personal DB MCP Server

Personal DB MCP Server

by itoufo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

delete_health_entry

Remove a health entry from the personal database by providing its unique entry ID. Delete unwanted or outdated health records to keep your stored health data accurate and up to date.

Instructions

健康エントリを削除

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": {
      "id": "<id>"
    },
    "name": "delete_health_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesエントリID (UUID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states the action ('delete') with no details on irreversibility, what happens to related data, or any side effects. This is a bare minimum disclosure for a mutating operation.

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

Conciseness4/5

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

The description is a single short sentence with zero waste, which is appropriately concise for a tool with one parameter. However, it errs on the side of under-specification rather than genuine conciseness.

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

Completeness2/5

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

For a destructive mutation tool with no annotations, no output schema, and a single-parameter input, the description should provide more context about the deletion behavior, irreversibility, or relationship to other health entry operations. The two-word description is inadequate for a delete operation.

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?

With 1 parameter at 100% schema description coverage, the schema already documents the 'id' parameter as 'エントリID (UUID)'. The description adds no additional meaning beyond the schema, which puts this at the baseline of 3 for good schema coverage.

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

Purpose3/5

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

The description '健康エントリを削除' (delete health entry) states the verb (delete) and resource (health entry), making the basic purpose clear. However, it does not distinguish itself from the many sibling delete tools like delete_hobby, delete_career_entry, etc. beyond the resource name itself.

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 guidance is given on when to use this tool versus alternatives such as update_health_entry, delete_custom_entry, or other delete tools. There is no context about prerequisites, such as needing an existing entry or undelete behavior.

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