Skip to main content
Glama
Sign In
doricomcp

doricomcp

by kulbiq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_library

Lists live Dorico library collections with IDs and names—including instruments, clefs, playing techniques, ornaments, tempo presets, and paragraph styles—so you can find and reference items by filter.

Instructions

Library entities (ids + names), live from Dorico: kInstrumentCollection, kClefCollection, kPlayingTechniqueAppearanceCollection, kOrnamentCollection, kTempoPresetCollection, kParagraphStyleCollection... [READ-ONLY: not yet confirmed by the live harness]

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": {
      "collection": "<collection>"
    },
    "name": "list_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNo
collectionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and offers only the hedged '[READ-ONLY: not yet confirmed by the live harness]' caveat. That caveat is genuinely useful — it warns that availability is unverified — but there is no indication of failure behavior, auth context, pagination, or whether the listed collections are exhaustive ('...').

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short and front-loaded with the useful payload (entities, ids + names, live from Dorico). But the collection list is a truncated comma-spliced run-on ending in an ellipsis, and the bracketed hedge reads as an authoring TODO rather than agent-facing guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value explanation is unnecessary, and the collection names plus the read-only caveat cover most of what an agent needs for a 2-parameter lookup. The gaps are filter semantics and whether the collection enumeration is closed, which is minor against the structured context available.

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 0%, so neither parameter is documented structurally. The description partially compensates by supplying example values for 'collection' (kInstrumentCollection, kClefCollection, kPlayingTechniqueAppearanceCollection), which is the meaning that parameter needs. The 'filter' parameter receives no attention at all, leaving its matching semantics unknown.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource (library entities, ids + names) and names concrete collections such as kInstrumentCollection and kClefCollection, so an agent can recognize the domain. However, it never states an explicit verb like 'list' and never says these strings are the valid values for the required 'collection' parameter; that link must be inferred from the ellipsis.

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

Usage Guidelines2/5

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

There is no when-to-use, when-not-to-use, or alternative routing. Nothing distinguishes this from discovery siblings like list_capabilities or describe_enums, which occupy a similar lookup niche, so the agent must guess based on the name alone.

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