Skip to main content
Glama
Sign In

CultureLib Discover

by io.github.tbalcinha
OverviewDiscussionsAdmin

search

Search the CultureLib catalog of French cultural events (theater, concerts, exhibitions, kids shows, guided tours) and their multi-reseller ticket offers. Returns matching events as citable documents; use fetch with a returned id to get full detail, prices and booking links.

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
queryYesFree-text search, e.g. "cantatrice chauve paris"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It states the tool returns citable documents and directs to `fetch` for more detail, but does not disclose rate limits, auth requirements, or idempotency. Basic transparency is present.

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 sentences front-load the essential purpose and action. Every word adds value; no redundancy. Highly concise.

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?

No output schema, but description explains return type (citable documents) and next step (`fetch`). Could elaborate on document structure, but sufficient for a search tool with one parameter and simple output.

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?

Schema coverage is 100%, baseline 3. The description adds example usage ('cantatrice chauve paris') and context of free-text search, enhancing the parameter semantics beyond the schema.

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

Purpose5/5

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

The description specifies the tool searches a catalog of French cultural events and multi-reseller ticket offers, with a clear verb and resource. It distinguishes from siblings by mentioning ticket offers and the use of `fetch` for full details.

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?

The description notes that `fetch` should be used for full detail, implying a workflow, but does not specify when to use `search` over sibling tools like `search_shows` or `whats_on`. No explicit when-not-to-use or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All CultureLib Discover toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources