Skip to main content
Glama
Sign In
evand-mcp

evand-mcp

by Hr-ArshA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Evand organizer

get_organization
Read-onlyIdempotent

Retrieve an Evand organization's profile and social links, plus its upcoming or past events, by slug or full URL. Use it to inspect organizers before deciding to follow or attend.

Instructions

Get an Evand organization's profile (bio, logo, social links, followers, event counts) and, by default, its current/upcoming events. Accepts an organization slug or full https://evand.com/organizations/ URL. Set include_past_events=true to list archived events instead.

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

Input Schema

NameRequiredDescriptionDefault
slugYesOrganization slug or full Evand organization URL.
events_limitNoMaximum events to include, 1-30. Default 12.
include_eventsNoInclude the organization's events. Default true.
include_past_eventsNoReturn archived/past events instead of upcoming events. Default false.
max_description_charsNoMaximum characters of organizer bio to return, 0-20000. Default 4000.

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, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the useful default that events are included in the response and that the past-events flag swaps which set is returned. It says nothing about error handling for a bad slug, truncation behavior, or response shape beyond the field list.

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?

Two sentences, front-loaded with what the tool returns, then input form, then the one behavioral toggle. Nothing is redundant or padded.

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 compensates by listing the profile fields returned and stating the default event inclusion. All five parameters are covered between description and schema. It lacks any note on failure modes for an unresolvable slug, which is the one remaining gap for a 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 slug, events_limit, include_events, include_past_events and max_description_chars are all documented in the schema. The description only restates the URL-or-slug input form and the include_past_events semantics, adding no meaning the schema does not already carry. 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?

Specific verb plus resource, and it enumerates what the profile contains (bio, logo, social links, followers, event counts), so the agent knows what comes back. It also states the accepted identifier forms. It stops short of naming search_organizations as the alternative, so sibling differentiation is only implied by the slug-based lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit guidance for one branch — default returns current/upcoming events, set include_past_events=true for archived ones. It never says when to pick this over search_organizations or get_event, so the agent must infer that this is the direct-lookup path when a slug or URL is already known.

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