Skip to main content
Glama

Virág — Manhattan flower delivery

Suggest card messages

suggest_card_message

Get ready-made messages for the handwritten card. Occasions: just_because, bad_week, apology, anniversary, birthday, romantic, new_relationship, congratulations, get_well, long_distance, mother, thank_you, new_baby, sympathy. Personalize one with details the user shared before ordering.

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": {
      "occasion": "<occasion>"
    },
    "name": "suggest_card_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
occasionYesOccasion key

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description must cover behavior. 'Get ready-made messages' implies that this is a retrieval rather than a generation step, which is useful, but the description does not say whether the tool has side effects, whether it stores anything, or what form the returned suggestions take.

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 begins with the purpose, and the workflow hint follows. The occasion list duplicates the schema enum and makes the prose longer than necessary. The final sentence is also terse and slightly ambiguous about what 'personalize' means operationally.

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?

This is a low-complexity, single-parameter tool with no output schema, and the description covers purpose, the supported occasions, and the point in the flow at which it is used. Because no output schema exists, it could do more to describe the shape of the returned messages (for example, how many suggestions there are), so this falls slightly short.

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%, and the single occasion parameter is documented with an enum, so the schema already explains the parameter. The description repeats the same occasion list in prose and adds only that the user-supplied details are for personalization. That baseline of 3 is therefore correct.

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 states a specific verb and resource: 'Get ready-made messages for the handwritten card.' This makes the tool's scope immediately clear, and it is easily distinguishable from the sibling tools (check_delivery, create_order, get_order_status, list_bouquets), none of which produce message content.

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 gives clear context: choose an occasion, personalize the message, and do so before ordering. This places the tool in the ordering workflow, which links it to create_order, but it does not state when not to use it or what alternative to choose, so it falls short of the top score.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.