Skip to main content
Glama
Sign In
ableton-mind

ableton-mind

by Pantani
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

session_diff

Compare a previous session snapshot with the current Live state to verify changes after mutations; returns added, removed, or changed paths with before/after values.

Instructions

Compare a previous session_snapshot with the current Live state. Use after a mutation batch to verify what actually changed; returns added/removed/changed paths with before/after values and a change count.

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": {
      "previous": "<previous>"
    },
    "name": "session_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
previousYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It describes the tool as a comparison that returns change details, implying no side effects. It could be more explicit about being read-only and non-destructive, but it adequately hints at safe 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?

The description is two sentences, concise and front-loaded with the core purpose. Every clause adds value without redundancy.

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?

Given the deep nesting of the input parameter and no output schema, the description provides a high-level overview of inputs and outputs but lacks specifics on how to acquire the snapshot or interpret the diff result. It is adequate but not fully comprehensive.

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?

Only one parameter exists with a complex schema and 0% schema description coverage. The description adds context by calling it a 'previous session_snapshot', but does not detail how to obtain or format it. The schema already defines the structure, so the description adds minimal new meaning beyond the schema.

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 clearly states the tool compares a previous session_snapshot with the current Live state, using specific verbs and resources. It uniquely distinguishes from sibling tools like session_get_info and session_snapshot by focusing on diffing.

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?

The description explicitly recommends using the tool after a mutation batch to verify changes, providing clear usage context. However, it does not mention when not to use it or potential alternatives, though none exist among siblings.

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