Skip to main content
Glama
Sign In
@formegifts/mcp

@formegifts/mcp

Official
by formegifts
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_wishlist

Update a wishlist's name, description, or event date by providing the wishlist ID. At least one field besides ID is required.

Instructions

Update a wishlist's name, description, or event_date by id. At least one field besides id is required.

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": "update_wishlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
descriptionNo
event_dateNo
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.5

TDQS

A3.7/5.0
Behavior3/5

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

The description confirms the tool performs a mutation (update) and mandates at least one additional field. However, it lacks behavioral details such as error handling (e.g., non-existent id), return value, or side effects. Since no annotations exist, the description bears full burden but only partially fulfills it.

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 that efficiently conveys the action, target fields, and the required condition. No superfluous words.

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?

Given the absence of output schema, annotations, and parameter descriptions, the description is insufficient for an agent to fully understand the tool's behavior. Missing details include success/error responses, what happens when a non-existent id is provided, and whether all fields are optional except id.

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 description coverage is 0%, so the description should compensate by adding meaning beyond the schema structure. It merely lists the fields (name, description, event_date, id) without providing additional context like format constraints (beyond what schema already specifies) or usage examples.

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 verb 'Update' and resource 'wishlist', and specifies the exact fields that can be updated (name, description, event_date). This distinguishes it from sibling tools like 'update_gift' and 'create_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?

The description provides a clear constraint 'At least one field besides id is required', which guides the correct invocation. However, it does not explicitly state when to use this tool versus alternatives or when not to use it.

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