Skip to main content
Glama

Get event details

get_event_detail
Read-onlyIdempotent

Get full details of an event by its id. イベントIDから詳細情報を取得する。

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": {
      "event_id": "<event_id>"
    },
    "name": "get_event_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the user's conversation: ja, en, zh or ko (default ja). Sets joino_url to the page in that languageja
event_idYesEvent id (UUID) returned by the search tools

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / event_id / description
      Added value: +"Event id (UUID) returned by the search tools"
    • addedInput schema / properties / lang / description
      Added value: +"Language of the user's conversation: ja, en, zh or ko (default ja). Sets joino_url to the page in that language"
  2. First observed

TDQS

C2.9/5.0
Behavior2/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 fully covered by structured data. The description adds nothing beyond that: no note on what happens with an unknown/stale id, no scope or locale side effects (e.g. that lang changes joino_url), no freshness caveats. The bar is low with rich annotations, but this text clears none of it.

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

Conciseness3/5

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

It is short and front-loaded, but the second sentence is a verbatim Japanese restatement of the first rather than new information, so a meaningful share of the text is duplication. Nothing is padded beyond that bilingual repeat.

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 two-parameter, read-only lookup with an output schema and complete annotation coverage, the essentials are present. What is missing is the one thing structured fields cannot supply: the workflow linkage to the search tools that produce event_id, and the significance of the lang side effect.

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%, including the non-obvious effect of lang on joino_url, so the schema carries parameter meaning entirely. The description only echoes that an id is required and adds no format, source, or locale detail. Baseline 3 applies 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: 'Get full details of an event by its id.' An agent can tell this is a single-record detail lookup, distinct from the sibling search_* tools. It stops short of naming any sibling for differentiation.

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 use this tool versus search_events or the other search siblings, and no stated prerequisite such as 'call after search_events returns an id'. The only hint at sequencing lives in the event_id schema field ('returned by the search tools'), not in the description.

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