Skip to main content
Glama
evand-mcp

evand-mcp

by Hr-ArshA

Search Evand organizers

search_organizations
Read-onlyIdempotent

Find organizations on Evand by name. Returns follower and event counts, organization slug, and supports sorting by followers, bestsellers, or partnerships to help you pick the right organizer.

Instructions

Search organizations that host events on Evand, by name. Returns follower/event counts and the organization slug. Sort by followers (default), bestsellers, or partnerships. Use get_organization for full details and their events.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, default 1.
sortNofollowers = most followed (default); bestsellers = most ticket sales; partnerships = Evand partners.
queryNoOrganization name search, e.g. 'ابرها' or 'CS50'.
per_pageNoResults per page, 1-50. Default 12.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile needs no restating. The description adds genuinely new behavior: the shape of results (counts plus slug) and the default sort order, which the agent would not know from annotations alone.

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 short sentences, front-loaded with purpose, then result shape, then routing to the sibling. No filler and nothing repeated.

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 summarizes what comes back (follower/event counts and slug) and the default ordering, which is enough to call it correctly. Pagination semantics are left entirely to the schema, which is acceptable given 100% coverage.

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%, and the description largely restates what the schema already documents (name search, sort options, followers default). It adds a concrete query example magnitude ('by name') but no new syntactic or interaction detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('Search organizations that host events on Evand, by name') plus the scope of what is returned (follower/event counts, slug). This clearly distinguishes it from get_organization, which is named as the detail-fetching counterpart.

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?

Explicitly routes the agent: use get_organization for full details and an organization's events, implying this tool is for discovery/listing only. It does not state exclusions such as what to do when the name query is empty or how this differs from search_events, so a small gap remains.

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