Skip to main content
Glama

Get session evidence for a track

get_track_evidence

Get the History session evidence for one track: session count, mean/median/min/max RMSSD (ms), mean heart rate (bpm), and the underlying sessions. Tracks with no sessions report session_count 0. Wellness music; not a medical device; rPPG-derived HRV values are estimates.

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": {
      "track_id": "<track_id>"
    },
    "name": "get_track_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
track_idYesTrack slug, e.g. midnight

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations present, the description carries the disclosure burden and does real work: it states the empty case ('Tracks with no sessions report session_count 0') and flags that HRV values are rPPG-derived estimates from a wellness product, not a medical device, so the agent can caveat results appropriately. It leaves unaddressed whether 'underlying sessions' results are paginated or bounded and whether any authentication is required.

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?

The return payload is front-loaded in the first sentence, and the empty-result edge case follows immediately; no filler. The closing disclaimer packs three separate claims into one semicolon chain, which is dense but carries real interpretation value.

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?

There is no output schema, so the description must explain the return shape, and it does by naming each statistic plus the list of underlying sessions. The remaining gap is that the structure, size, or ordering of the 'underlying sessions' list is not characterized.

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% and the single track_id parameter is already documented with a slug example ('midnight'). The description adds only 'for one track', which restates the schema rather than extending it with format or lookup-failure semantics.

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?

The description uses a specific verb ('Get') plus a well-scoped resource ('History session evidence for one track') and enumerates exactly what is returned (session count, mean/median/min/max RMSSD, mean heart rate, underlying sessions). Nothing among the siblings (purchase_track, verify_session, list_catalog, purchase_album) resembles a read of session metrics, so the intent is unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied: the description makes clear this is the way to retrieve session-derived HRV/HR statistics for a single track, but it offers no explicit when-to-use/when-not framing or pointers to any related retrieval path. Given the siblings do not overlap functionally, the missing guidance is low-risk but still absent.

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.