Skip to main content
Glama
Sign In

upTake

by me.uptake
OverviewDiscussionsAdmin

Link a post to a move

uptake_link_post_move

Makes a post count for an open move of this week: publishing the post completes the move.

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": {
      "post_id": "<post_id>",
      "move_id": "<move_id>"
    },
    "name": "uptake_link_post_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
move_idYesOpen move from moves_this_week in uptake_overview. Publishing the post then completes it.
post_idYesId from uptake_posts or uptake_write_post.
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

A3.5/5.0
Behavior4/5

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

Annotations already declare it as a non-readonly, non-destructive, non-idempotent operation. The description adds useful behavioral context beyond annotations: linking makes the post count for an open move, and publishing the post completes the move. It does not cover error cases or repeated-link behavior, so not a 5.

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?

The single sentence is front-loaded and wastes no words, but the phrasing 'makes a post count' is slightly indirect compared to simply saying 'links a post to a move'.

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 rich schema descriptions and annotations, most structured context is already present. The description supplies the key effect and temporal scope, but it could say more about what happens on failure or when the post is already linked.

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 every parameter is already well documented in the input schema. The description adds no parameter-specific syntax or edge-case guidance, making 3 the appropriate baseline.

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?

The description states a specific effect: making a post count for an open move this week, which implicitly links the post to the move. It does not explicitly differentiate this tool from siblings like uptake_plan_post or uptake_write_post, so it falls short of a 5.

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

Usage Guidelines2/5

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

It identifies the relevant move context ('open move of this week') but gives no explicit guidance on when to choose this tool over alternatives, nor any prerequisites or exclusions. The agent must infer usage from the title and schema.

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