Skip to main content
Glama

Asana

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.9/5.0
Behavior5/5

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

Annotations declare readOnlyHint, idempotentHint, and destructiveHint. The description adds scoping details ('Scoped to your identifier') and the effect of omitting the key (list all keys), providing context beyond annotations.

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 sentences, each earning their place. The first states the core function, the second adds context. No redundancy or wordiness.

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?

For a read tool with no output schema, the description covers what to expect (value or list of keys), scoping, and usage. It could mention potential output limits or pagination, but overall it is sufficiently complete.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds meaning: 'omit the key argument' to list keys. It clarifies the single parameter's two modes, improving understanding beyond the schema.

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 specifies 'Retrieve a value previously saved via remember, or list all saved keys', clearly identifying the verb and resource. It also distinguishes from siblings by mentioning 'remember' and 'forget', which are listed as sibling tools.

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

Usage Guidelines5/5

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

The description provides explicit guidance: 'Use to look up context the agent stored earlier... without re-deriving it from scratch.' It also implicitly advises when not to use (for saving or deleting) by pairing with remember and forget.

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

All Asana 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

B3.3/5.0
Disambiguation2/5

The tool set mixes Asana project management tools with a large number of Pipeworx data retrieval tools. Within the Pipeworx subset, tools like ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded have overlapping purposes, and multiple prediction market tools exist (e.g., polymarket_arbitrage, polymarket_edges). This creates ambiguity and potential for misselection.

Naming Consistency2/5

Tool names lack a consistent pattern. Some use 'asana_' prefix, others use descriptive phrases (e.g., 'compare_entities', 'generate_llms_txt'), and some are single verbs (e.g., 'forget', 'remember'). Mix of different conventions leads to unpredictability.

Tool Count2/5

37 tools is high for a server named 'Asana', yet only 6 tools are Asana-specific. The majority are Pipeworx tools unrelated to Asana. This overloading makes the server feel bloated and off-purpose.

Completeness2/5

For Asana functionality, the set is incomplete: missing update/delete task, project management features, etc. The Pipeworx tools are extensive but irrelevant to the server's stated purpose, leaving the Asana workflow with notable gaps.

Resources