Skip to main content
Glama
Sign In
LiveSession MCP

LiveSession MCP

by Uri-Rosen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

find_progressions

Read-only

Search 45 named chord progressions by name, genre, or mood, then select one to play via write_named_progression; leave the query empty to list all options.

Instructions

The progression library (45 named progressions): search by name, genre or mood — "pop", "sad", "mizrahi", "jazz", "house", "cinematic", "israeli"... Empty query lists them all. Play one with write_named_progression.

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

Input Schema

NameRequiredDescriptionDefault
queryNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real context beyond that: the fixed library size (45), the searchable fields, and the empty-query behavior that returns everything. Return-format details are unnecessary because an output schema exists.

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?

Three short sentences, front-loaded with what the tool is, then the query semantics, then the next-step tool. The example terms earn their space by showing an agent what kind of strings actually match.

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?

For a single-optional-parameter read-only lookup with an output schema and clear annotations, nothing an agent needs to call it correctly is missing: it knows the library scope, how to enumerate everything, and which tool to call next.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the query parameter has no description in the schema, so the description carries the full burden — and does: it names the searchable facets (name, genre, mood) and supplies concrete vocabulary examples. The default/empty-string behavior is also spelled out, which the schema only hints at via `default: ""`.

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 and resource ('search the progression library', 45 named progressions) and names the dimensions searchable (name, genre, mood). It is clearly separable from siblings like write_progression, write_chords and write_named_progression, which generate rather than look up material.

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?

Explicitly explains that an empty query lists all 45 progressions, and points to write_named_progression as the follow-up action to play a result. It does not cover when an agent should prefer a free-form generator (write_progression) over a named lookup, but the alternative named is the relevant one for this 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