Skip to main content
Glama

La Cartelera

Search shows, comedians and venues

search
Read-onlyIdempotent

Search by name across upcoming shows (next 60 days), comedians and venues. Query of 2+ characters.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows per group (1-100).
queryYesText, e.g. a comedian, venue or show name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds a genuinely non-obvious behavioral constraint: results are confined to shows in the next 60 days. It stops short of describing grouping or ordering of returned rows.

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 short sentences with no filler. The 60-day scope is placed immediately after the resource list, and the query-length constraint follows as a compact qualifier.

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?

With no output schema, the description should clarify what comes back — the schema's 'Max rows per group' hints at grouped results, but the description never confirms that results are partitioned by entity type or how they are ordered. It covers inputs and scope adequately but leaves the return shape to inference.

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 100%, so both parameters are already documented, and the baseline is 3. The description contributes one extra semantic detail not in the schema — the 2+ character minimum for the query string — but says nothing further about how 'limit' behaves.

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 specific verb ('Search') and enumerates the three resource families searched (upcoming shows, comedians, venues), plus a scope limit of 60 days. It does not explicitly distinguish itself from siblings like find_shows or get_comedian, so an agent must infer the routing from the multi-entity scope rather than being told.

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?

Usage is implied: this is the name-based, cross-entity lookup, as opposed to the single-entity getters in the sibling list. There is no explicit statement of when to prefer this tool over find_shows, nor any exclusion or prerequisite, so the guidance remains inferential.

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