Skip to main content
Glama
Sign In

goldseam

by com.ksaworks
OverviewDiscussionsAdmin

Playlist Read

playlist_read
Read-only

Read one section named in a manifest, in full: give unitid for a section of a school's policy (from playlist_policy_open), or checklist_id for a section of a checklist's playlist (from playlist_open). A section over 60,000 characters is returned in parts: the answer carries part and next_part, and you ask again with part set to next_part until next_part is null. Pages come in cleaned text, the same text every source quote is checked against. Read-only.

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": {
      "section": "<section>"
    },
    "name": "playlist_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
partNoOptional: which part of a long section, from 1 (default 1)
unitidNoThe school whose policy section to read; give this or checklist_id, not both
sectionYesThe section's name exactly as the manifest gives it
checklist_idNoThe checklist whose playlist section to read; give this or unitid, not both

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnlyHint, the description discloses non-obvious behavior: sections over 60,000 characters are split and the caller must loop on part/next_part until null, and the returned text is the cleaned canonical text that source quotes are validated against. That paging contract is exactly the kind of detail an agent cannot infer from annotations or schema.

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 dense but well-ordered paragraph: purpose, input sourcing, pagination loop, text semantics. The trailing 'Read-only.' restates the annotation and is the only wasted clause, but it is short and harmless.

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?

With no output schema, the description still explains the shape of the response (part, next_part, cleaned text) and the termination condition, so an agent can call and iterate correctly. Nothing material is missing for a four-parameter read tool.

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%, so the baseline is 3, but the description adds real meaning: which source tool supplies unitid vs checklist_id, and the semantics of part as a continuation cursor driven by next_part rather than an arbitrary page number.

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 and resource ('Read one section named in a manifest, in full') and immediately scopes the two input modes to their source tools (playlist_policy_open for unitid, playlist_open for checklist_id). An agent can distinguish this from playlist_open/playlist_policy_open without opening any schema.

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?

It tells the agent exactly where each identifier comes from ('from playlist_policy_open', 'from playlist_open') and how to continue reading a long section via next_part. It does not explicitly state when not to use this versus the sibling open tools, but the prerequisite chaining gives strong practical routing.

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