Skip to main content
Glama

ArtistAlly

by sh.alchemylab.artistally
OverviewDiscussionsAdmin

Search conventions

artistally_search_conventions
Read-onlyIdempotent

Search fan conventions (furry, anime, gaming) across 51 US and Canadian metro areas. Returns upcoming conventions by default (soonest first); set include_past to search the archive too. Filter by text, community, region, state, metro, or date range. Returns dates, venue, location, registration windows and table costs, plus a canonical ArtistAlly URL per convention.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results, default 20.
metroNoMetro slug from artistally_get_coverage, e.g. "atlanta", "toronto".
queryNoFree-text match on convention name, venue, or city, e.g. "Otafest" or "Atlanta".
stateNoTwo-letter US state or Canadian province code, e.g. "GA", "TX", "ON".
offsetNoPagination offset, default 0.
regionNoCoverage region, e.g. "Southeast", "Midwest", "West Coast", "Canada". Valid values come from artistally_get_coverage.
communityNoFilter by community: furry, anime, gaming, or multi (multi-genre).
include_pastNoInclude conventions that have already finished (default false). Past results are still sorted soonest-first; use starts_after/starts_before to target a specific year.
starts_afterNoOnly conventions starting on or after this date (YYYY-MM-DD).
starts_beforeNoOnly conventions starting on or before this date (YYYY-MM-DD).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include_past
      Added value: +{
+  "description": "Include conventions that have already finished (default false). Past results are still sorted soonest-first; use starts_after/starts_before to target a specific year.",
+  "type": "boolean"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, openWorld=false), the description discloses default ordering (upcoming, soonest first), the include_past toggling behavior, that past results remain sorted soonest-first, and the set of returned fields including a canonical URL. This adds valuable behavioral context not present in the structured annotations.

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 sentences, front-loads the core function, and packs essential details (geography, default behavior, filters, output fields) without redundancy. No filler words or repetition of schema property names verbatim, except for the necessary include_past explanation.

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

Completeness5/5

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

With 10 optional parameters and no output schema, the description provides crucial output semantics (dates, venue, location, registration windows, table costs, URL) and default/filter behaviors. It fully equips an agent to understand what the tool returns and how to narrow results. The only minor omission is pagination, but offset/limit are documented in the schema.

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%, so baseline is 3. The description goes slightly beyond the schema by grouping filters conceptually ("text, community, region, state, metro, or date range") and explicitly highlighting the include_past flag as the way to search the archive. This helps an agent conceptualize parameter combinations, though it does not detail each parameter's syntax.

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 opens with a specific verb and resource: "Search fan conventions" across defined geographies, and later details what is returned (dates, venue, etc.). It clearly distinguishes itself from siblings by focusing on search/listing capabilities rather than single-record retrieval, coverage discovery, or open registrations.

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

Usage Guidelines4/5

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

The description gives clear context for when to use this tool: when a user needs to find conventions across metro areas with filters and date ranges. It does not explicitly name alternatives or exclusion criteria (e.g., 'for a specific convention ID use get_convention'), but the purpose is unambiguous enough for an agent to select it appropriately among sibling tools.

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

All ArtistAlly 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