Skip to main content
Glama
Sign In
doricomcp

doricomcp

by kulbiq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

describe_property

Retrieves the type, display name, and allowed enum values for a Dorico event property so you can understand valid settings before editing a score.

Instructions

Type, display name and enum values of an event property (e.g. kNoteVelocity, kEventColour). [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": {
      "name": "<name>"
    },
    "name": "describe_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose that the operation is READ-ONLY while candidly flagging that this has not been confirmed by the live harness — useful behavioral context an agent cannot get elsewhere. It says nothing about behavior on an unknown property name or whether lookups can fail, which leaves gaps for a tool with zero annotation coverage.

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 compact sentence plus a bracketed caveat, front-loaded with the returned fields. The noun-phrase construction lacks an explicit verb, but nothing is padded or redundant.

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?

An output schema exists, so return values need not be explained, and the read-only caveat is a plus. However, for a lookup tool with 0% parameter coverage and no annotations, the absence of usage routing against describe_enums/describe_commands and of error behavior leaves it only minimally adequate.

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% and the single parameter is documented only as a generic string 'name'. The examples (kNoteVelocity, kEventColour) usefully convey the expected identifier format, which is real added value, but case sensitivity, accepted namespaces, and valid-value sourcing remain unstated.

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

Purpose4/5

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

The description names the resource (an event property) and precisely enumerates what is returned: type, display name, and enum values, with concrete examples (kNoteVelocity, kEventColour). The verb is only implied by the tool name, and there is no explicit differentiation from siblings like describe_enums or describe_commands, so it falls short of a 5.

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 guidance and no mention of alternatives such as describe_enums or set_property. An agent must infer from the name alone that this is the lookup counterpart to set_property.

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