Skip to main content
Glama
Sign In

goldseam

by com.ksaworks
OverviewDiscussionsAdmin

Playlist Open

playlist_open
Read-only

Start or reuse one checklist's playlist: its requirements, with its school's policy, set out as an ordered sequence of lines. It needs a saved school policy and names playlist_policy_open as the next call when there is none. Answers hit (the stored playlist, its playlist_id and status), or stale or miss with a manifest of sections to read with playlist_read: stored_rows, requirements, requirements_html, courses, one linked:<capture_file> for each page the requirement section links to that the cabinet holds, and policy. Links the cabinet does not hold are listed by URL. On stale it also returns the stored playlist. You read the sections, reason over them yourself, and send the lines with playlist_save.

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": {
      "checklist_id": "<checklist_id>"
    },
    "name": "playlist_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
checklist_idYesThe checklist, by its checklist_id from a CourseShelf answer

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true; the description goes far beyond by enumerating the three outcome classes (hit, stale, miss) and exactly what each returns, including that stale also yields the stored playlist. It also discloses that some links are returned by URL rather than fetched, which the agent could not otherwise predict.

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?

Purpose and prerequisite come first, followed by return shapes and the closing workflow step, so it is front-loaded and information-dense with little waste. It loses a point for the run-on middle sentence packed with jargon like 'manifest,' 'cabinet,' and 'hit/stale/miss' that is never defined inline.

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 one-parameter, read-only tool with no output schema, the description fully carries the burden: it covers prerequisites, failure routing, the complete section manifest, and the hand-off to playlist_save. An agent could invoke and act on this tool correctly without any further information.

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

Parameters4/5

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

Schema coverage is 100% on the single checklist_id parameter, so the schema does the documentation work. The description adds only the mild clarification that the playlist belongs to one checklist, though that framing is useful for understanding the scoping.

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 opens with a specific verb pair and resource: "Start or reuse one checklist's playlist," then defines what a playlist is (requirements plus school policy as an ordered sequence of lines). This is distinguishable at a glance from siblings like playlist_read, playlist_save, and playlist_policy_open.

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?

It states an explicit prerequisite (a saved school policy) and routes to playlist_policy_open when that is absent, then closes the loop by naming playlist_save as the destination once the agent has read and reasoned over the sections. The workflow position of this tool is unambiguous.

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

All goldseam toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources