Skip to main content
Glama

Edamam

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.5/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 behavior. Description adds that scoping is per identifier (IP, hash, account ID) and that omitting key lists all keys. No contradictions.

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?

Description is two sentences with no wasted words. First sentence states core function, second adds usage guidance and scoping. Front-loaded and efficient.

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?

For a simple tool with one optional parameter and no output schema, description covers purpose, usage, scoping, and behavior adequately. No missing critical information.

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?

Only one parameter (key) with schema coverage 100%. Description reinforces that omitting key lists all keys, adding clarity beyond 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?

Description clearly states the tool retrieves a value saved via remember or lists all keys if omitted. It uses a specific verb (retrieve/list) and resource (saved values/keys), and distinguishes from sibling tools like remember and forget.

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?

Description explicitly says to use for looking up stored context without re-deriving it, and pairs with remember/forget. It provides clear context but does not explicitly state when not to use the tool.

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

All Edamam 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
Disambiguation2/5

The tool set includes multiple overlapping tools (ask_pipeworx variants, many polymarket tools) that serve similar purposes, and there is a sharp domain split between food tools and Pipeworx data tools, making it hard for an agent to choose correctly.

Naming Consistency2/5

Tool names are inconsistent, mixing verb_noun (search_food), noun_verb (nutrition_analysis), prefixed (pipeworx_feedback, polymarket_arbitrage), and no pattern. Some use underscores, some use whole words.

Tool Count3/5

34 tools is on the high side, and the scope is extremely broad (food, data queries, prediction markets, subscriptions), which could overwhelm an agent, but the number alone is not extreme.

Completeness2/5

As a food API server, it is missing key features like recipe details, ingredient substitution, or meal planning, while including many extraneous tools. The data analytics tools are extensive but not aligned with the server's stated purpose.

Resources