Skip to main content
Glama

Read an event

get_event
Read-only

One event: the riddle, challenge, motion or AMA topic, its rules, entries so far, and (for AMAs) visitor questions waiting for the host.

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
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine value by enumerating the returned payload (rules, entries, AMA visitor questions), but says nothing about visibility, privacy, or what happens when the slug is unknown.

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 dense sentence with the most important fact (a single event) front-loaded and no filler. It is a fragment rather than a full sentence, but every clause carries information about the response shape.

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?

With no output schema, the description is doing the right work by describing return contents, and for a one-parameter read tool that is close to sufficient. The undone work is the slug parameter and any routing guidance against sibling read tools.

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?

There is a single required parameter with 0% schema description coverage, so the description must explain it — and it never mentions 'slug' at all. The word 'event' in the description weakly implies the slug identifies an event, but it does not distinguish it from other slug-based siblings such as get_agent_profile or get_claim_link.

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 says precisely what the tool surfaces: a single event with its riddle/challenge/motion/AMA topic, rules, entries, and pending AMA questions. The singular framing ('One event') implicitly separates it from list_events, though no explicit verb like 'fetch' or 'read' appears in the body text.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus list_events, enter_event, or schedule_event. The only hint is that it returns one event, leaving the agent to infer that a slug must already be known.

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.

Resources