Skip to main content
Glama

Suggest a piece for an occasion

suggest_art
Read-only

Suggest pieces suited to an occasion or a mood, such as a birthday, a thank-you, the end of a project, a launch, a welcome or a farewell. Useful when an agent wants a small gift for its person. Free. Returns suggestions with reasons, previews and buy URLs.

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

Input Schema

NameRequiredDescriptionDefault
countNo
occasionYesThe occasion or mood, in plain words, e.g. "birthday", "thank you for the help", "we shipped the project".
recipientNoOptional: a few words about who it is for, used only to vary the suggestion.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered by structured data. The description adds genuinely new context — it is "Free" and returns "reasons, previews and buy URLs" — which compensates for the absent output schema. It still says nothing about result limits, latency, or failure modes when an occasion is unmatched.

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?

Three short sentences, front-loaded with purpose and followed by intended use and return contents. The one-word "Free." sentence earns its place by answering a cost question an agent may need before calling.

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 low-risk read-only suggestion tool with three simple parameters, the definition covers purpose, use case, cost, and return shape, offsetting the missing output schema. Minor gaps remain around result quantity and what happens when no piece matches the occasion.

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 coverage is 67%, with occasion and recipient documented inline, so the schema carries most of the load. The description restates the occasion concept in prose but adds no format, phrasing, or interaction detail beyond what the schema already provides, and the count parameter gets no treatment in either place.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ("Suggest pieces suited to an occasion or a mood") and enumerates concrete occasions, so the tool is distinguishable from retrieval siblings like get_art or list_art. It stops short of naming or contrasting those siblings explicitly, which keeps it from a 5.

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 gives a clear situational cue: "Useful when an agent wants a small gift for its person," which tells the agent the intent-driven context for calling it. There is no explicit when-not guidance or named alternative for browsing vs. targeted retrieval, so it is clear context without exclusions.

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