WeekendSeek

by dev.workers.weekendseek.weekendseek-mcp-open

search_venues

Read-onlyIdempotent

Search museums/galleries that have a venue page on weekendseek.com (name, address, category, tier, venue page URL). Response is {total, offset, items}: when total > offset + len(items), call again with a larger offset to fetch the remaining pages.

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

Input Schema

Name	Required	Description
`city`	No	Covered bucket/group/locality ID or city/region name or alias. Use resolve_location for ambiguity. Omit for all.
`lang`	No	Language of display fields. Default: en.
`limit`	No
`offset`	No	Rows to skip for pagination (result order is stable). Page while offset < total.
`keyword`	No	Substring matched against venue name (case-insensitive).
`category`	No	Venue category (e.g. 'museum', 'gallery').

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds useful scope details (only venues with a venue page), the response envelope {total, offset, items}, and the pagination termination condition. It does not discuss permissions or rate limits, but that bar is lower with annotations 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?

The description is two front-loaded sentences with no wasted text. The returned fields are compactly listed and the pagination rule is stated directly.

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?

With no output schema, the description usefully provides the response shape and pagination rule, and annotations cover safety behavior. The schema covers most parameter details, though the description still lacks selection guidance among sibling tools.

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 83%, so the baseline is 3. The description adds return fields and pagination behavior, but does not meaningfully explain city, keyword, or category semantics beyond what the schema already provides, and the offset logic is already documented in 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?

The description states a specific verb and resource: search museums/galleries that have a venue page on weekendseek.com. It is clear what the tool returns, but it does not explicitly distinguish itself from sibling search_exhibitions beyond the resource noun.

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?

The description gives no when-to-use or when-not-to-use guidance and does not name alternatives like search_exhibitions or list_cities. The pagination sentence explains invocation mechanics, not tool selection.

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

All WeekendSeek tools Inspect

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

Need Help?