Skip to main content
Glama
io.github.ryanmat/logicmonitor

io.github.ryanmat/logicmonitor

by ryanmat

get_session_history

Read-onlyIdempotent

Lists recent tool call history for the current session, returning up to a configurable number of entries (default 10, maximum 50).

Instructions

List recent tool call history

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": "get_session_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum entries to return (max 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is fully covered without the description. The only added behavioral word is 'recent', which is undefined — no time window, no ordering (newest-first?), and no indication of what a history entry contains.

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?

One short, front-loaded sentence with no filler. It is lean rather than padded, though the leanness edges into under-specification rather than efficiency.

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

Completeness3/5

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

The tool is simple (one optional parameter, no output schema, strong annotations), so the description needs only a little more: what 'recent' means and the ordering of results. As written it is adequate but leaves the agent guessing about scope and recency.

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 optional 'limit' parameter is documented with its default and max of 50, so the schema carries the burden. The description adds nothing about the parameter, which is acceptable given the baseline for fully documented schemas.

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 pairs a specific verb ('List') with a clear resource ('recent tool call history'), which is enough for an agent to know it retrieves logged invocations rather than session variables or context. It stops short of distinguishing itself from near siblings such as get_session_context, and it never clarifies whether the history is scoped to the current session or all sessions.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisite, and no named alternative. An agent must infer from the name alone that this is the audit/tracing tool rather than the session-state tool.

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

Deploy Server

Other Tools