Skip to main content
Glama
Sign In

upTake

by me.uptake
OverviewDiscussionsAdmin

Update a move

uptake_update_move
Destructive

Marks one of this week's moves as done (or reopens it), edits its title or reason, or dismisses it with a reason. Only when the maker asks.

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": {
      "move_id": "<move_id>",
      "change": "<change>"
    },
    "name": "uptake_update_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
whyNoedit: new one-sentence reason.
noteNodismiss: a few words from the maker.
titleNoedit: new title, an imperative of at most 80 characters.
changeYesdone: the maker did it (added to the journal). reopen: undo done. edit: new title and/or why. dismiss: remove it, with a reason.
reasonNodismiss: not_relevant (not relevant), already_done (already done), wrong_numbers (wrong numbers), not_my_channel (not a channel i use), too_much_time (too much time), other (other).
move_idYesId from moves_this_week in uptake_overview.
projectNoWhich project: its id or site (example.com) from uptake_projects. Optional when the maker has a single project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and non-idempotent, and the description is consistent with that (dismiss "removes" the move). It adds useful behavioral context — that 'done' writes to the journal and 'reopen' undoes it — though it does not say whether a dismissal can be recovered or what state a dismissed move ends in.

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?

Two short sentences, zero filler, with the operational scope front-loaded before the consent constraint. Every clause earns its place.

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 seven parameters fully described in schema and no output schema, the description covers enough for correct invocation. Minor gaps remain around the 'this week' boundary and irreversibility of dismissal, but nothing blocking.

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% and each mode value, the reason enum, and the move_id/project sourcing are all documented in the schema itself. The description only summarizes the four modes without adding format, constraint, or cross-parameter dependency detail beyond that.

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 set of verbs (mark done, reopen, edit, dismiss) against a specific resource (one of this week's moves), which maps exactly onto the four-value 'change' enum. It is clearly distinct from siblings like uptake_add_move or uptake_dismiss_idea.

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?

"Only when the maker asks" is an explicit gating condition on when to call, which is unusually clear consent guidance for a mutation tool. It does not, however, name alternatives or exclusions — e.g. it never contrasts dismissing a move here with uptake_dismiss_idea.

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

All upTake toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources