Skip to main content
Glama
Sign In
Personal DB MCP Server

Personal DB MCP Server

by itoufo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

delete_skill

Remove a skill entry from your personal database by providing its unique ID, ensuring AI services no longer receive outdated or incorrect skill data for personalized responses.

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_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesエントリID (UUID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior1/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. 'スキルを削除' does not disclose whether deletion is permanent/reversible, requires confirmation, affects related entries (e.g., entries referencing this skill), or has any side effects. For a destructive operation with zero annotation coverage, this is a critical gap.

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

Conciseness3/5

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

The description is extremely short (single phrase). While concise, it's more under-specification than intentional brevity. It conveys minimal information but is certainly not verbose or wasteful.

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?

The tool is simple (1 parameter, no output schema), which lowers complexity. However, it's a destructive operation with no annotations, no behavioral disclosure, and no explanation of consequences. For a delete operation, the description is inadequate even at low complexity.

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 'id' parameter is fully documented as an entry UUID in the schema. The description adds nothing about the parameter, but baseline 3 applies since the schema handles parameter documentation.

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

Purpose2/5

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

The description 'スキルを削除' (Delete skill) states a verb+resource but provides no scope, no behavior details, and no differentiation from the many sibling delete_* tools. It's minimal and functional but lacks specificity about what 'skill' refers to or any distinguishing context.

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 on when to use this tool versus alternatives. While it's obvious from the name that it deletes skills, there's no mention of prerequisites, cascading effects, or when NOT to use it. No alternatives 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