Skip to main content
Glama

The Cultural Signal

Art fair calendar

fair_calendar
Read-only

Upcoming art fair editions with dates, city, venue and a permanent page URL. Optional region filter.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
regionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine value by listing the returned fields in the absence of an output schema, but it says nothing about ordering (presumably chronological), how many records come back, or the effect of limit, which is the main behavioral unknown.

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 short sentences with no filler, and the core resource statement is front-loaded. The trailing 'Optional region filter' fragment is efficient but slightly under-integrated rather than wasteful.

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 two-parameter read tool with no output schema, the description covers the essential return fields and the region filter. The missing piece is limit behavior and result ordering, which an agent would need to call this correctly without inspecting the schema.

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 description coverage is 0%, so the description must carry parameter meaning. It only mentions the region filter, and even then adds nothing beyond the enum already in the schema ('optional' merely restates that required is empty). The limit parameter, including its default of 20 and maximum of 60, is not addressed at all.

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 resource (upcoming art fair editions) and enumerates the fields returned (dates, city, venue, permanent page URL), which clearly separates it from siblings like art_jobs and latest_stories. It is a noun phrase rather than a verb+resource statement, but an agent can still tell what the tool yields.

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 only implied: 'Upcoming art fair editions' suggests a forward-looking calendar lookup, and 'Optional region filter' hints at narrowing. There is no explicit when-to-use or when-not-to-use guidance, though the siblings are different enough that no disambiguation is strictly required.

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