Skip to main content
Glama

events

Dated events in Albuquerque (shows, markets, comedy, classes) from each venue's own announcement. Defaults to today through 7 days out. Dates are YYYY-MM-DD.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
date_toNo
date_fromNo
neighborhoodNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It usefully states the data provenance (each venue's own announcement) and the default date window, but says nothing about result ordering, pagination behavior via limit, or whether results are scraped live versus cached.

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 the resource and scope, with no wasted wording. The date-format note is placed directly after the default-window sentence where it is most needed.

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

Completeness2/5

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

For a 5-parameter, zero-annotation, no-output-schema tool, the description is thin: three of five parameters have no semantics anywhere, and return shape or ordering is never hinted at. It covers the date behavior adequately but not enough to let an agent call this correctly with query or neighborhood filters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% across 5 parameters, so the description must compensate. It explains date_from/date_to implicitly through 'Defaults to today through 7 days out' and the YYYY-MM-DD format, but leaves query, neighborhood, and limit completely undefined in both schema and description.

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?

Names the resource (dated events in Albuquerque) and enumerates the categories covered (shows, markets, comedy, classes), plus the data provenance ('from each venue's own announcement'). It lacks an explicit verb like 'list' or 'search', but an agent can still tell this apart from place-oriented siblings such as get_place and search_places.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives or exclusions relative to the sibling tools. The default 7-day window is stated, which weakly implies a browse-events use case, but the agent must infer all routing decisions.

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