Skip to main content
Glama
Sign In
Torus

Torus

by sekhar14
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

recent_records

Read-only

List recent research sessions with their saved claims, theses, relations, and sources, newest first, to review what Torus recorded and find records to undo.

Instructions

List what the most recent research sessions recorded (claims, theses, relations, sources, ruled-out ideas), newest session first, with each session's id and whether each record can still be undone. Read-only. Use it when the user asks what Torus saved, then pass the session id and records to undo_records to revert the unwanted ones.

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

Input Schema

NameRequiredDescriptionDefault
sessionsNoHow many recent sessions to list (1-10)

Output Schema

NameRequiredDescriptionDefault
sessionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • changedInput schema / properties / sessions / description
      Previous value: -"Most recent sessions"New value: +"How many recent sessions to list (1-10)"
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description is consistent ('Read-only'). It adds behavior beyond the annotations: newest-session-first ordering and a per-record flag for whether the record can still be undone, which is meaningful for chaining into undo_records. It stops short of discussing session scope limits or what happens when no sessions exist.

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?

Compact and front-loaded: purpose first, then ordering, then the usage trigger and chaining advice. The parenthetical record list is slightly long but each item adds disambiguation value.

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?

A single-parameter read-only list tool with an output schema, so return values need not be described; the description still covers ordering, session id, and undoability, and points to the chained tool. An agent has everything needed to select and invoke it.

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 the single `sessions` parameter is documented inline with its 1-10 range and default of 1. The description only implies the window via 'most recent' and adds no format or default 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 (list) and resource (records from the most recent research sessions), enumerating the record kinds it covers (claims, theses, relations, sources, ruled-out ideas). The ordering ('newest session first') and the inclusion of session id plus undoability make it clearly distinguishable from siblings like timeline or undo_records.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('when the user asks what Torus saved') and an explicit next step: pass the returned session id and records to `undo_records`. Both the when and the follow-on alternative are named, leaving nothing to inference.

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