Skip to main content
Glama

Clickup

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

TDQS

A4.3/5.0
Behavior4/5

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

Description adds value beyond annotations: explains key-value storage, scoping by identifier, and session persistence details. No contradiction with annotations (idempotentHint=true, destructiveHint=false).

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?

Four sentences, no wasted words. Purpose front-loaded, then usage, then behavior. Efficient and clear.

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?

Given two required parameters with full schema coverage and no output schema, description fully covers purpose, usage, storage behavior, and interaction with sibling tools. No gaps.

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?

Input schema provides 100% coverage with descriptions for key and value. Description adds examples and context but does not enhance parameter semantics beyond schema; baseline score appropriate.

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?

Clearly states the tool saves data for reuse across conversations/sessions, with specific verb 'save' and resource 'data'. Distinguishes from siblings recall and forget by naming them and explaining the pairing.

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?

Specifies when to use: when discovering something worth carrying forward. Provides context on persistence (24 hours for anonymous) and mentions complementary tools. Lacks explicit 'when not to use' but still strong guidance.

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

All Clickup toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation3/5

Many tools have distinct purposes, but there is overlap among query tools (ask_pipeworx, ask_pipeworx_grounded, deep_research) and among prediction market tools. Detailed descriptions help differentiate, but the large number of tools increases chance of misselection.

Naming Consistency2/5

Naming is highly inconsistent, mixing snake_case and camelCase conventions. ClickUp tools use 'clickup_' prefix while Pipeworx tools have varied patterns (ask_, scan_, validate_, etc.). No unified convention across the set.

Tool Count2/5

35 tools is excessive for a server named 'Clickup', with only 6 ClickUp-specific tools. The remaining 29 are from Pipeworx, which is unrelated. The count is inappropriate for the server's stated purpose.

Completeness2/5

The ClickUp integration is incomplete, missing basic CRUD operations like update and delete tasks. The Pipeworx side is comprehensive but not relevant to the server's name. For a ClickUp server, coverage is poor.

Resources