Skip to main content
Glama
Sign In

upTake

by me.uptake
OverviewDiscussionsAdmin

Add a move

uptake_add_move

Adds a move of the maker's own to this week's list.

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": {
      "title": "<title>"
    },
    "name": "uptake_add_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
whyNoOne sentence on why it matters this week.
titleYesAn imperative of at most 80 characters ("Answer the r/SaaS thread about pricing").
networkNoNetwork the move is about, if any.
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

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the description's remaining burden is contextual. It doesn't warn that non-idempotent calls create duplicates, what the required project context implies, or where the move lands beyond 'this week's list' — notable omissions for a write tool.

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?

A single front-loaded sentence with no filler. It is efficient, though the extreme brevity shades into under-specification rather than pure conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter write tool with no output schema, the description omits what is returned, whether duplicates are created on repeat calls, and how the move relates to projects or networks. The schema covers parameters, but the behavioral context is too thin.

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%, with clear per-parameter docs (imperative title format, one-sentence why, project id or site). The description adds nothing to those semantics, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb and resource ('Adds a move') and adds scope ('this week's list', 'the maker's own'), which is more than the title alone. However, 'move' is never defined for an agent unfamiliar with the domain, and there is no differentiation from siblings such as uptake_update_move or uptake_link_post_move.

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?

There is no guidance on when to use this versus uptake_update_move (edit an existing move) or the idea/plan tools. The only implicit hint is 'this week's list', which doesn't tell the agent when to reach for this tool.

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