Skip to main content
Glama
evand-mcp

evand-mcp

by Hr-ArshA

Search Evand events

search_events
Read-onlyIdempotent

Search Evand public events by keyword, city, category, online status, price, or start date; returns paginated event cards with slugs and URLs, and can include archived past events.

Instructions

Search upcoming public events on Evand (evand.com) by Persian/English keyword, city, category, online status, price and start date. Returns compact event cards with slugs and URLs plus pagination. Set include_past=true to search Evand's archive of past events. If a city or category is rejected, call list_cities or list_categories to discover the accepted names/slugs.

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_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity name or slug, e.g. 'تهران', 'tehran', 'اصفهان'. Multiple cities can be comma-separated.
pageNoPage number, starting at 1. Default 1.
sortNonearest = soonest first (default, same as Evand's 'زمان'); trending = most popular; bestsellers = most tickets sold; randomness = random; start_date = start date ascending.
queryNoFree-text search, e.g. 'هوش مصنوعی', 'برنامه نویسی', 'startup', 'DevOps'.
onlineNotrue = only online/webinar events; false = only in-person events; omit = both.
categoryNoCategory name or slug, e.g. 'تکنولوژی', 'technology', 'هوش مصنوعی', 'ai', 'فین-تک'.
per_pageNoResults per page, 1-50. Default 12 (Evand's page size).
max_priceNoMaximum ticket price in Iranian Toman (inclusive).
min_priceNoMinimum ticket price in Iranian Toman (inclusive). 0 includes free events.
include_pastNoSearch archived (past) events instead of upcoming events. Default false.
start_date_toNoLatest event start date, inclusive, as YYYY-MM-DD in Tehran time (Gregorian).
start_date_fromNoEarliest event start date, inclusive, as YYYY-MM-DD in Tehran time (Gregorian).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds value beyond them by disclosing the result shape (compact cards with slugs and URLs), the presence of pagination, and the archive-switch behavior of include_past — useful because no output schema exists. Auth requirements and rate limits remain unstated.

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?

Three sentences, each doing distinct work: purpose and filters first, then return shape and pagination, then the archive toggle and fallback routing. It is front-loaded and free of filler.

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 12 optional parameters and no output schema, the description covers the essentials an agent needs: what it searches, how results are shaped, pagination, the past/upcoming switch, and recovery from rejected city or category values. Defaults for sort and per_page live only in the schema, but that is a minor gap rather than a blocking one.

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 every parameter already has its meaning and format documented, including the sort enum and date format. The description only restates the filter dimensions and adds the one behavioral note about include_past switching to the archive; it adds no syntax or format detail beyond 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 names a specific verb and resource (search public events on Evand) and enumerates the filter axes: keyword, city, category, online status, price, and start date. It implicitly separates itself from get_event and search_organizations by saying results are 'compact event cards with slugs and URLs,' but it never names the sibling it is not, leaving that distinction to inference.

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 gives a concrete routing rule ('If a city or category is rejected, call list_cities or list_categories to discover the accepted names/slugs') and a clear condition for the archive mode ('Set include_past=true'). There is no explicit statement of when NOT to use this tool, for example in favor of search_organizations or get_event.

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