Skip to main content
Glama
Sign In

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

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.1/5.0
Behavior4/5

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

The annotations already declare that this is a read-only, idempotent, non-destructive, closed-world operation, and the description adds useful behavioral context: default sorting, archive behavior, and the kinds of fields returned. It does not discuss authentication, rate limits, or pagination behavior, but those are less critical given the explicit 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 compact and front-loaded: the search scope and default behavior come first, followed by filtering and return-value details. Every sentence contributes useful information without repetition or filler.

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?

Although there is no output schema, the description summarizes the return payload (dates, venue, location, registration windows, table costs, canonical URL), which is exactly what an agent needs to know. Combined with the rich schema and annotations, the definition is complete for correct tool selection and invocation.

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 100%, so all ten parameters are already documented in detail, including defaults, formats, and examples. The description restates the available filter categories and include_past behavior but adds little syntax or semantic detail beyond what the schema already provides.

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 fan conventions across 51 US and Canadian metro areas, with clear scope and supported communities. It does not explicitly distinguish this search tool from sibling tools such as artistally_get_convention or artistally_list_open_registrations, so it falls short of a 5.

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?

It clearly explains default behavior (upcoming conventions, soonest first) and how to include past events via include_past. It also enumerates the available filter dimensions, but it does not name alternatives or explicitly say when to prefer this tool over the sibling lookup or registration-list 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