Skip to main content
Glama

Get current draft work

get_current_work
Idempotent

Open or resume your private editing draft on a personal board you can publish to. This is a write, not a pure read: when no draft exists it creates one, with its first checkpoint, in your private workspace. Returns the draft id, whether the saved head moved since you started, the current checkpoint id to pass to push_board, and recent checkpoint ids for restore_checkpoint. Does not upload or publish.

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": {
      "board": "<board>"
    },
    "name": "get_current_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardYesYour board: handle/slug or a boardrepo.com URL.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the surprising side effect that a missing draft gets created along with its first checkpoint in a private workspace. It also clarifies the "Does not upload or publish" boundary and what state is returned (draft head movement), which the readOnlyHint=false/idempotentHint=true flags alone would not convey.

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?

Front-loads the core action and the write caveat, which is the right order. The return-value enumeration is somewhat redundant with the presence of an output schema, but the mapping of checkpoint id to push_board and checkpoint ids to restore_checkpoint still earns its space.

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?

For a one-parameter tool with full schema coverage, annotations, and an output schema, the description covers everything an agent needs: creation side effect, workspace privacy, non-publishing scope, and how the returned ids feed sibling tools. Nothing material is missing.

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 the single board parameter is already fully documented with format hints in the schema. The description adds only marginal meaning by framing the board as a personal, publishable board; baseline 3 applies when the schema does the heavy lifting.

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: "Open or resume your private editing draft on a personal board you can publish to." It also implicitly separates this from push_board and restore_checkpoint, which it names as downstream consumers, so an agent can place it in the workflow without opening schemas.

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 clear context for calling it (open or resume a draft, creating one when none exists) and points to push_board and restore_checkpoint as follow-on steps. It does not explicitly exclude or compare against a pure-read alternative such as get_board, so no explicit when-not guidance.

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