Skip to main content
Glama

Plan a night out for a group of friends

plan_night_out
Read-onlyIdempotent

Plan dinner, drinks and a live music venue in one city for 2 to 6 friends. Give the city and each friend's name with 1 to 4 music artists, movies, TV shows or books they love. Optionally give an exact night date as YYYY-MM-DD; Qloo then filters venues by that date's weekday only, not by exact opening times, travel or availability. Qloo's cross-domain taste graph turns that shared taste into real venues. Each stop is the venue whose least happy friend is happiest, and Qloo explainability names the favourites behind it, with the share of each friend's taste.

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": {
      "city": "<city>",
      "members": "<members>"
    },
    "name": "plan_night_out"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity for the night out, for example Lisbon or New York.
dateNoOptional exact night date as YYYY-MM-DD. Qloo filters places by that date's weekday only.
membersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / date
      Added value: +{
      +  "description": "Optional exact night date as YYYY-MM-DD. Qloo filters places by that date's weekday only.",
      +  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +  "type": "string"
      +}
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so safety is covered; the description adds real behavioral substance beyond that. It discloses that date filtering is weekday-only and does NOT account for opening times, travel or availability, plus the maximin selection rule and that explainability output names favourites with taste shares.

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?

Front-loaded with the core action and inputs in the first two sentences, then the caveats and output behavior. Five sentences with minimal waste, though the 'least happy friend is happiest' phrasing and explainability sentence are slightly ornate for what they convey.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by describing the return shape: an itinerary of stops, each chosen by a maximin rule, accompanied by named favourite artists with share-of-taste. Combined with the input requirements and date caveat, an agent has everything needed to call and interpret it.

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?

With 67% schema coverage the baseline is around 3, but the description goes further: it restates the 2-6 member bound, the 1-4 likes bound, the acceptable like types, and explains the date parameter's semantics (weekday filtering only) in a way the schema does not fully convey. Per-member name constraints are left to the schema.

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?

States a concrete verb and deliverable ('Plan dinner, drinks and a live music venue in one city') with an explicit scope of 2 to 6 friends, so an agent knows exactly what it produces. It never references the sibling find_common_ground, so the agent gets no help distinguishing the two.

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?

Requirements are clear (city plus each friend's name and 1-4 favourites, optional date), and the date caveat explains a usage limitation. But it never says when this tool is preferred over find_common_ground or when not to use it, so selection guidance is only implied.

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