Skip to main content
Glama

weekly_nights

Recurring weekly nights in Albuquerque: trivia, karaoke, bingo, live music, comedy, open mic. Filter by category or day (Monday..Sunday).

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": "weekly_nights"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayNo
limitNo
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It reveals nothing about return shape, ordering, pagination behavior, or whether results are cached/static listings, beyond the passing implication of a 'limit' default of 30. For a discovery tool with zero annotation coverage, this is a notable gap.

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 compact sentences with the resource and coverage types front-loaded and the filtering guidance second. No filler, though the list of night types crowds out room that could have been spent on parameter details.

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

Completeness3/5

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

For a simple three-parameter, no-output-schema read tool, the description covers what the results are and how to filter them. It still leaves the agent guessing about the limit/pagination semantics and the valid category values relative to an otherwise 0%-covered schema.

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 0%, so the description must compensate. It usefully pins the 'day' parameter to Monday..Sunday values and clarifies that 'category' refers to night types, but leaves the category vocabulary unspecified and says nothing about 'limit' or its default of 30.

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 names a concrete resource (recurring weekly nights) and enumerates the content types covered (trivia, karaoke, bingo, live music, comedy, open mic), plus the location (Albuquerque). It implicitly describes a listing/lookup tool and is distinguishable from a generic 'events' or 'search_places' sibling by the 'recurring weekly' framing, though it never states the verb explicitly.

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?

It says how to narrow results ('Filter by category or day') which implies when the tool is useful, but gives no guidance on when to prefer it over siblings like events, open_now, or search_places, and no exclusions or prerequisites.

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