Skip to main content
Glama

My recent sessions

my_history
Read-only

Use this when the user asks what they listened to recently or how much time they have listened. Not for medical questions, emergencies or a crisis. Not for general chat about meditation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "my_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
tapNoThe token from keep_progress for this conversation; leave empty if there is none.
limitNoHow many sessions to return. Default 10.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered without the description's help. The description adds the domain boundaries (no medical/crisis use), which is genuinely useful context beyond annotations, but says nothing about result volume, ordering, or the purpose of the tap token. With annotations doing the heavy lifting, a 3 is appropriate.

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?

Three short sentences, with the positive use case front-loaded before the exclusions. The three separate 'Not for' clauses are slightly repetitive but each guards against a distinct misuse, so they largely earn their place.

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?

This is a simple two-parameter read tool with full schema coverage and annotations covering safety, so little is required. The description covers when to call it and when not to; the only real gap is that it never states what the response contains (session entries vs. aggregate minutes), which matters slightly since there is no output schema.

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 both parameters (tap, limit) carry their own descriptions including the default of 10 and the max of 20. The description adds no meaning beyond that, which is the expected baseline when the schema fully documents inputs.

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 frames the tool as answering 'what they listened to recently' and 'how much time they have listened', which pins down both the resource (listening history) and the two query shapes it serves. It does not name a sibling such as find_sessions to differentiate itself, so it falls short of a 5.

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?

It gives explicit trigger conditions (recent listening, total listening time) plus three clear exclusions: medical questions, emergencies/crisis, and general chat about meditation. It stops short of routing the agent to an alternative tool for those excluded cases or for other session queries, so the guidance is strong but not complete.

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