Skip to main content
Glama

Viventii Events, Leisure, POIs, Tickets & Ticket Resale

Get Public Organizer Profile & Upcoming Events

get_organizer_profile
Read-onlyIdempotent

Loads a verified Viventii organizer public profile (by slug or user ID) along with their upcoming public events.

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": {
      "identifier": "<identifier>"
    },
    "name": "get_organizer_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoPreferred language code (default: de)
identifierYesOrganizer public slug or user ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description does add value by saying the profile is 'verified' and 'public' and that upcoming events are bundled in, which tells the agent the scope of returned data. It does not say what happens for an unknown/invalid identifier, whether unverified organizers are excluded, or how far 'upcoming' extends.

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?

One sentence with no filler, and the key facts — what is loaded and how it is identified — come first. It is efficiently sized for a two-parameter read tool; there is just no additional structure beyond that single clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only tool with a fully documented schema and no output schema, the description covers the essentials: the resource, the lookup key, and that events are included. It leaves open what the profile record contains and the time window for 'upcoming' events, which an agent would want when deciding whether this call suffices.

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 coverage is 100% — both parameters carry descriptions, including the locale enum with its default. The description's '(by slug or user ID)' restates the schema's identifier description rather than adding format or validation detail. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb and resource: it loads an organizer's public profile plus their upcoming public events, keyed by slug or user ID. That is clearly distinguishable from the sibling event-search and discovery tools, none of which fetch organizer profiles. It stops short of naming an alternative, but the resource itself is unambiguous.

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?

Usage is only implied — an agent can infer it should call this when it needs organizer details or an organizer's event lineup. There is no explicit when-to-use, when-not-to-use, or pointer to a sibling for related needs. Adequate but with a clear gap.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.