mcp-score

by tskovlund

Overview Schema Source Related Servers Discussions Admin

Python

Local

undo_last_action

Revert the last edit in your MuseScore file to restore the prior version of your composition.

Instructions

Undo the last change in the connected application.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 26, 2026
- addedOutput schema / $defs
```
Added value: +{
+  "CommandResult": {
+    "additionalProperties": true,
+    "type": "object"
+  }
+}
```
- addedOutput schema / properties / result / $ref
```
Added value: +"#/$defs/CommandResult"
```
- removedOutput schema / properties / result / title
```
Removed value: -"Result"
```
- removedOutput schema / properties / result / type
```
Removed value: -"string"
```
First observedv0.1.0May 29, 2026

TDQS

A3.7/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Undo the last change' and does not clarify whether the operation is destructive, whether it undoes only changes made by this integration vs. all app changes, or how many steps of undo history are available.

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?

A single, front-loaded sentence that communicates the entire purpose of a zero-parameter tool. There is no wasted phrasing, and no additional length is warranted for such a simple operation.

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?

The tool is simple, has zero parameters, and has an output schema, so the description need not explain return values. However, for a mutating operation with no annotations, it would be more complete to clarify the scope of 'last change' and any side effects.

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?

The tool has zero parameters, so no parameter documentation is needed. The schema coverage is effectively complete, and the baseline for a parameterless tool is met.

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 names a specific action ('Undo') and a clear target ('the last change in the connected application'). It is unambiguous and distinguishable from all sibling tools, none of which are undo operations.

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

Usage Guidelines3/5

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

The description implies when this tool should be used: after an unwanted change in the connected application. However, it does not explicitly state when not to use it or mention any alternative, though no direct undo alternative exists among the siblings.

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