Skip to main content
Glama

Virág — Manhattan flower delivery

List flower bouquets

list_bouquets

List the 3 flower bouquets Virág delivers in Manhattan, NYC (Sweet $119, Romantic $229, Grand Gesture $749). Prices include flowers, a handwritten card, delivery and tax. Also returns delivery rules and how many pilot orders remain.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_bouquets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: 'List' establishes a read-only operation, and it discloses that the response also includes delivery rules and remaining pilot order capacity — an operational detail an agent could not otherwise anticipate. It stops short of stating response shape or any limits, but nothing is misleading.

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?

Two front-loaded sentences with the catalog and pricing stated first and the extra return content second; the parenthetical price list is dense but earns its space. No filler wording.

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?

There is no output schema, so the description must disclose return values, and it names the bouquet set, pricing inclusions, delivery rules, and remaining pilot orders. For a zero-parameter read tool this is close to complete, with only the exact response structure unspecified.

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?

The tool takes zero parameters, so there is no parameter meaning to add; the description correctly avoids inventing inputs. Baseline 4 applies for a parameterless tool.

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?

Description states a specific verb+resource ('List the 3 flower bouquets') and immediately enumerates the exact contents with names and prices, so an agent knows precisely what this returns without opening a schema. It is clearly distinct from check_delivery and create_order by being a pure catalog read.

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

Usage Guidelines3/5

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

Usage is only implied: listing the catalog before ordering is the obvious pattern, but the description never says when to call this versus check_delivery or create_order, nor does it state prerequisites. Adequate but leaves routing to inference.

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.