Skip to main content
Glama
evand-mcp

evand-mcp

by Hr-ArshA

Get similar Evand events

get_similar_events
Read-onlyIdempotent

Find similar events to a given Evand event using its slug or full URL, returning 1-12 recommendations for follow-ups like 'what else is like this?'

Instructions

Get Evand's recommendations for events similar to a given event. Useful for 'what else is like this?' follow-ups. Accepts a slug or full Evand event URL.

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

Input Schema

NameRequiredDescriptionDefault
slugYesEvent slug or full Evand event URL.
limitNoNumber of similar events, 1-12. Default 6.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety and determinism profile is covered structurally. The description adds that results are algorithmic 'recommendations' rather than exhaustive matches, but says nothing about result ordering, whether fewer results than requested may return, or what an event record contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core action and then the usage cue and accepted input form. Nothing is padded, though the third sentence largely duplicates the slug parameter description.

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?

For a two-parameter read-only lookup with full schema coverage and annotations carrying the safety profile, the description covers what the tool does and when to use it. The only omission is any hint about the shape of the returned recommendation list, which is a minor gap given no output schema exists.

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%: the slug parameter already documents 'Event slug or full Evand event URL' and limit documents the 1-12 range and default of 6. The description only restates the slug-or-URL acceptance, so it adds no meaning beyond the schema; baseline 3 applies.

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 opens with a specific verb and resource: 'Get Evand's recommendations for events similar to a given event.' That clearly separates it from get_event (single event lookup) and search_events (query-driven search), even though no sibling is named explicitly.

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?

'Useful for "what else is like this?" follow-ups' gives a concrete scenario for reaching for this tool. It stops short of explicit exclusions or naming search_events as the alternative for keyword-driven discovery, so it is clear context without full routing rules.

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