Skip to main content
Glama

Save as a new score

save_new_score

Save the draft as a new score in the linked account's library (never overwrites one; a free account keeps 3 scores), under a title (default the score's own). Needs the account linked.

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": {
      "draft": "<draft>"
    },
    "name": "save_new_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftYesThe draft: the id a previous tool gave (draft).
titleNoThe title in the library (default the score's own).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare a non-destructive, non-idempotent, closed-world write, and the description adds real value on top: it never overwrites an existing score, a free account is capped at 3 scores, and the account must be linked. The quota limit is a genuinely useful behavioral trait. It does not say what happens when the cap is hit, which is the remaining gap.

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 with the action first and qualifications nested in parentheses. No filler, and every clause (non-overwrite, quota, title default, account link) carries information.

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?

An output schema exists, so return values need no explanation, and the description covers the mutation's safety profile, the account prerequisite, and the quota constraint. For a two-parameter save tool this is sufficient to call it correctly.

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 100%, so both the draft id and the title default are already documented in the schema; the description only restates the title default and adds no format or syntax detail. Baseline 3 is appropriate when the schema carries the parameter semantics.

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?

States a specific verb and resource (save the draft as a new score) plus destination scope (the linked account's library), and clarifies non-overwriting semantics that separate it from an update tool. It never names a sibling such as create_score or import_score, so the differentiation is implicit rather than explicit.

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?

Gives usable context: this is the non-destructive save path (never overwrites), and a prerequisite (the account must be linked). It stops short of explicitly naming the alternative tool to use when the intent is to overwrite an existing score, leaving that inference to the agent.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources