Skip to main content
Glama

Add a session to My day or take one out

event_my_day_change
Idempotent

Adds one session to the signed-in person's My day for an event, or takes one out ("add this session to my day", "take the keynote out of my day"). action is "add" or "remove", with no default. session is either the session id from events_whats_on or event_my_day, or the session's name as the person says it. When the name fits more than one session, the reply is code WHICH_SESSION with choices, one row per session it fits, and nothing changes. The change shows on the pass page and the event page the next time they load. Needs the person signed in (an unauthenticated call is answered with the sign-in prompt) and eventIdOrName.

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>",
      "session": "<session>",
      "action": "<action>"
    },
    "name": "event_my_day_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesREQUIRED. "add" or "remove". There is no default.
sessionYesREQUIRED. The session id from events_whats_on or event_my_day, or the session's name as the person says it.
eventIdOrNameYesREQUIRED. The event id or the event name as events_list spells it.

Output Schema

NameRequiredDescriptionDefault
okNo
codeNo
countNo
errorNo
actionNo
choicesNo
eventIdNo
inMyDayNo
messageNo
sessionNo
writtenNo
myDayUrlNo
servedByNo
sessionsNo
suggestionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / sessions
      Added value: +{
      +  "items": {
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / written
      Added value: +{
      +  "type": "integer"
      +}
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (which already declare non-read-only, non-destructive, idempotent), the description discloses three behaviors an agent could not infer: ambiguity handling (returns code WHICH_SESSION with one choice row per matching session and changes nothing), auth behavior (unauthenticated calls get a sign-in prompt), and propagation timing (change appears on the pass page and event page on next load). This is exactly the kind of context annotations cannot carry.

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?

It is front-loaded with the core act and packs a lot of high-value behavior into one dense paragraph with no filler sentences. The heavy use of parentheticals and inline backticked codes makes it slightly harder to scan than a short bulleted structure would be.

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 three-required-param mutation tool with an output schema, the description covers everything an agent needs: auth precondition, target event identification, session reference formats, ambiguity fallback, and when the effect becomes visible. Nothing essential is left to inference.

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%, so the baseline is 3; the description earns a bump by clarifying that `session` accepts either an id sourced from events_whats_on or event_my_day, or a spoken name, and by describing what happens when a name is ambiguous. The `action` no-default rule and the eventIdOrName sourcing from events_list are mirrored in the schema rather than added.

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 opens with a concrete verb pair (adds/takes out) and names the exact resource (one session in the signed-in person's My day for an event). An agent immediately knows this is a per-person itinerary mutation, not a general session-record edit. It does not explicitly distinguish itself from the similarly named sibling event_session_add, which is the only material gap.

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?

The two quoted user utterances ("add this session to my day", "take the keynote out of my day") give clear situational triggers, and the add/remove duality of the tool is stated up front. There is no explicit when-not clause and no sibling is named as an alternative, so it falls short of the 5 bar.

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