Skip to main content
Glama
Sign In

wawesome

by io.wawesome
OverviewDiscussionsAdmin

Show what a draft changed

get_draft_changes
Read-onlyIdempotent

Shows what a draft changed against the Version it started from. It answers the paths the draft added, changed and deleted, and its revision. It is how to pick up a draft in a new conversation.

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": {
      "function_name": "<function_name>",
      "draft_id": "<draft_id>"
    },
    "name": "get_draft_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_slugNoThe App's slug. Omitted, the Tenant's default App.
draft_idYesThe draft, as 'open_draft' or 'list_drafts' names it.
function_nameYesThe Function's slug.

Output Schema

NameRequiredDescriptionDefault
addedNo
draftYes
changedNo
deletedNo
warningYesWhat the next CLI deploy does to this draft's change. Null where the live Version did not come from the CLI.
app_slugYes
function_nameYes
live_from_cliYesTrue where the live Version was deployed with the CLI, which is most likely from a repository.
live_version_numberYesThe Version that is live. Null where none is.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / warning / description
      Previous value: -"What to tell the person before they rely on this draft. Null where there is nothing to tell."New value: +"What the next CLI deploy does to this draft's change. Null where the live Version did not come from the CLI."
  2. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only the shape of the report (added/changed/deleted paths and revision), which is largely output detail; it says nothing about auth requirements, scope, or limits.

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?

Three short sentences with the core behavior front-loaded and no filler. The middle sentence restates result contents slightly redundantly with the output schema, but overall it is efficient and readable.

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?

With full schema coverage, complete safety annotations, and an output schema that carries the return shape, the description only needs to convey purpose and context, which it does. What is missing is routing guidance among the many sibling draft/version tools.

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 description coverage is 100%, so app_slug, draft_id, and function_name are already documented in the schema, including how draft_id maps to open_draft/list_drafts. The description adds no additional parameter meaning, so the baseline of 3 applies.

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?

States a specific verb and resource: shows what a draft changed relative to the Version it started from, and enumerates the reported output (added/changed/deleted paths plus revision). This diff-oriented scope inherently separates it from siblings like list_drafts, open_draft, edit_draft, and preview_draft.

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?

The closing sentence gives a concrete usage context: 'It is how to pick up a draft in a new conversation.' That tells an agent when this is the right call, but no alternatives or exclusions are named (e.g., when to prefer preview_draft or list_drafts instead).

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

All wawesome toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources