Skip to main content
Glama
Sign In
@formegifts/mcp

@formegifts/mcp

Official
by formegifts
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_gift

Delete a gift by ID. With confirm: true, permanently removes the gift; without confirmation, returns a dry-run summary showing what would be deleted.

Instructions

Delete a gift by id. Without confirm: true, returns a dry-run summary. Pass confirm: true to actually delete.

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

Input Schema

NameRequiredDescriptionDefault
idYes
confirmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.5

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses the dry-run behavior, which is a key safety trait. It doesn't mention irreversibility, but the dry-run mitigates that concern.

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?

Two sentences, front-loaded with the main action, no redundant words. Every sentence serves a purpose.

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 delete tool with a safety feature, the description covers the core behavior, parameters, and usage flow. No output schema exists, but the description is sufficient.

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

Parameters4/5

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

Schema coverage is 0%, so description compensates by explaining the confirm parameter's role. The id parameter is implied but not elaborated beyond the schema's format. The explanation adds value.

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 starts with 'Delete a gift by id', providing a specific verb and resource. It clearly distinguishes from siblings like create_gift or delete_wishlist.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains the dry-run vs actual delete behavior via the confirm parameter, guiding safe usage. While it doesn't explicitly state when not to use it, the safety mechanism is well explained.

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