Skip to main content
Glama

Clickup

by io.github.pipeworx-io

Recall

recall
Read-onlyIdempotent

Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key to retrieve (omit to list all keys)

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive. The description adds behavioral details: behavior when key is omitted (list all), scoping by identifier, and the pairing with remember/forget. No contradiction.

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?

The description is concise (three sentences) and front-loaded with the core action. Every sentence adds value without redundancy.

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?

The description covers tool purpose, usage modes, scoping, and related tools. While it doesn't describe return value format explicitly, the context is sufficient for a simple tool with no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single parameter. The description adds semantic meaning beyond the schema: clarifies the effect of omitting the key (list all keys) versus providing it (retrieve single value).

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?

The description clearly states the tool's purpose with specific verbs ('retrieve', 'list') and resource ('saved values'). It distinguishes from siblings by mentioning 'remember' and 'forget' and explains the two modes (single key retrieval vs listing all keys).

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?

The description provides good usage context: looking up prior context like ticker, address, notes. It mentions scoping and pairing with remember/forget. It lacks explicit when-not-to-use or alternatives, but the context is clear enough.

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