Skip to main content
Glama

Show the sessions in the person's My day

event_my_day
Read-only

The sessions the signed-in person saved to My day for one event ("what is in my day", "my saved sessions"), earliest first. Each row carries the title, whenLocal (the spoken local time), the room, its speakers, and ended (true once the session is over). The reply also carries myDayUrl, which opens My day on the event page. It is the same list the pass page and the event page show: a session saved there is here, and the reverse. Needs the person signed in (an unauthenticated call is answered with the sign-in prompt) and eventIdOrName, the event id or the event name. An empty sessions means nothing is saved for that event yet; event_my_day_change adds one.

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": {
      "eventIdOrName": "<eventIdOrName>"
    },
    "name": "event_my_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventIdOrNameYesREQUIRED. The event id or the event name as events_list spells it.

Output Schema

NameRequiredDescriptionDefault
okNo
codeNo
countNo
errorNo
eventIdNo
messageNo
myDayUrlNo
servedByNo
sessionsNo
timezoneNo
suggestionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so the safety profile is covered. The description still adds real value: sign-in is required and an unauthenticated call returns a sign-in prompt, ordering is earliest first, `ended` marks finished sessions, and the list is identical to what the pass and event pages show. Missing details like pagination or result limits keep this from a 5.

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?

Front-loaded with what the tool returns, then behavior, then requirements, so an agent gets the essentials first. It is slightly long for a one-parameter read tool, with return-field detail that the output schema also carries, but no sentence is pure filler.

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

Completeness5/5

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

For a one-parameter read tool with full schema coverage, an output schema, and annotations, the description covers purpose, ordering, auth prerequisite, empty-result semantics, and the sibling that mutates the list. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter is already documented as the event id or name as events_list spells it, so the schema does the heavy lifting. The description reinforces the requirement and the id-or-name duality, and notes the tool is scoped to exactly one event, which clarifies the parameter's role in the call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource: the sessions the signed-in person saved to My day for one event, with example user phrasings in parentheses. It distinguishes itself from event_my_day_change, which is named as the tool that adds a session, so an agent can separate the read from the write without opening schemas.

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?

Gives clear usage context through the quoted intents ("what is in my day", "my saved sessions") and routes the add case to event_my_day_change. It also explains that an empty `sessions` means nothing is saved yet, which prevents a false-negative interpretation. It stops short of an explicit when-not-to-use rule, but the sibling routing covers the main fork.

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