Skip to main content
Glama

ForeverVow

List wedding invite designs

list_designs
Read-only

List ForeverVow's Indian wedding invitation designs (free and premium), each with a short description and a sample invite link. Use it to help the couple choose a design before create_invite.

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

Input Schema

NameRequiredDescriptionDefault
styleNoOptional filter: Rajasthani designs or other Indian designs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful data beyond that: results include both free and premium designs, each with a short description and a sample invite link. It does not say how many designs are returned or whether results are paginated.

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 tightly written sentences with zero waste; the payload description comes first and the workflow guidance second. Nothing is repeated from the schema or annotations.

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?

For a simple read-only, zero-required-parameter list tool with no output schema, the description covers purpose, return contents, and workflow context. Only minor gaps remain, such as result count or pagination behavior.

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 style parameter is documented with an enum in the schema, so the schema carries the parameter meaning. The description does not elaborate on the style filter or its enum values, so baseline 3 applies.

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?

States a specific verb ("List") and resource ("ForeverVow's Indian wedding invitation designs"), and even clarifies the scope (free and premium) and the per-item payload (short description and sample invite link). It distinguishes itself from the sibling create_invite by positioning itself as the step before it.

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?

Explicitly gives the usage context: "Use it to help the couple choose a design before create_invite," which routes the agent relative to the sibling tool. It does not state any when-not conditions, so it falls short of full alternative/exclusion coverage.

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.

Resources