Skip to main content
Glama
Sign In
evand-mcp

evand-mcp

by Hr-ArshA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Evand event details

get_event
Read-onlyIdempotent

Retrieve full public details for a single Evand event by slug or URL, including speakers, schedule, tickets, capacity, price, venue, organizer, categories, tags, and refund policy.

Instructions

Get full public details for a single Evand event: description, speakers/organizers, schedule/showtimes, tickets and remaining capacity, price, venue/location, organizer, categories, tags and refund policy. Accepts an event slug (from search_events) or a full https://evand.com/events/ URL. Use include_description=false for a smaller response.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesEvent slug (e.g. 'devops-w8') or full Evand event URL.
include_descriptionNoInclude the long description (sections, speakers). Default true.
max_description_charsNoMaximum characters of description text to return, 0-40000. Default 8000. Set 0 to skip.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the description's added value is the payload-shape disclosure: it lists the returned public fields and offers a response-size lever via include_description. It does not mention error behavior for an invalid slug, rate limits, or whether private/unlisted events are inaccessible, which keeps it just short of a 5.

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 the resource and its returned fields, followed by input format and then the size optimization. No filler and no repetition of the annotations, which already carry the safety hints.

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?

There is no output schema, and the description compensates by enumerating the returned field groups, which is what an agent needs to decide whether to call it. Combined with the accepted input format and the size control, nothing material is missing for a single-read lookup tool.

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 three parameters are already documented, including that slug accepts a slug or a full Evand URL. The description largely restates that and adds only the rationale that include_description=false yields a smaller response; it says nothing extra about max_description_chars beyond what the schema states. Baseline 3 is appropriate.

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+resource (get full public details for a single Evand event) and enumerates exactly what is returned: description, speakers, schedule, tickets/capacity, price, venue, organizer, categories, tags, refund policy. It also distinguishes itself from search_events by naming it as the source of the slug, so an agent can tell it apart from the search siblings without opening a schema.

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?

Gives clear context: use it for a single event, obtain the slug from search_events, and set include_description=false when a smaller response is wanted. It stops short of explicit exclusions (e.g., when to prefer get_similar_events or search_events instead), so it is strong context but not full when/when-not guidance.

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

Deploy Server

Other Tools