Skip to main content
Glama
Sign In

Anry

by io.anry.mcp
OverviewDiscussionsAdmin

Get session journey

get_session
Read-onlyIdempotent

The ordered in-session journey for one session id (from list_sessions): the page path plus the interaction timeline (page views, clicks, custom events, purchases), oldest event first, with a dashboard replay link. Complements list_sessions with what happened inside a single session. Returns event metadata only, never replay/DOM content.

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": {
      "site_id": "<site_id>",
      "session_id": "<session_id>"
    },
    "name": "get_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYesSite id from list_sites (UUID)
session_idYesSession id from list_sessions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (read-only, idempotent, non-destructive, closed world), yet the description adds real value: event ordering (oldest first), the inclusion of a dashboard replay link, and an explicit boundary that only event metadata is returned and never replay/DOM content. It does not mention any cap on the number of events or timeline truncation, which is the main unaddressed behavior.

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

Conciseness5/5

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

Three sentences, front-loaded with the resource and its payload, then the relationship to a sibling, then the scope limitation. Every sentence carries distinct information with no filler.

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

Completeness4/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 correctly takes on the burden of describing return content (page path, event timeline, replay link) and its limitations. The only gap is volume/ordering metadata such as whether the timeline is bounded or paginated for large sessions.

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% and both parameters are fully documented in the schema, including that they are UUID/ids sourced from list_sites and list_sessions. The description repeats the list_sessions provenance for session_id but adds no new format or constraint detail, so the baseline 3 applies.

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 specific verb and resource ("ordered in-session journey for one session id") and enumerates the returned payload: page path, interaction timeline of page views, clicks, custom events and purchases, ordered oldest first. It also distinguishes itself from list_sessions and, via the "never replay/DOM content" line, from replay-oriented siblings.

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?

Explicitly tells the agent where the input comes from ("from list_sessions") and frames the tool as the drill-down for a single session, so the use case is unambiguous. It stops short of naming get_session_replay or get_session_frames as the alternatives for replay/DOM, leaving that routing implicit.

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

All Anry toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources