Skip to main content
Glama

xkcd

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 already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds valuable behavioral context beyond annotations, such as scoping to a user identifier (anonymous IP, BYO key hash, or account ID) and the dual-mode behavior of listing all keys when the key argument is omitted. This contextual information is not present in the 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?

The description is concise and front-loaded with the primary action. Every sentence adds unique value: purpose, usage examples, scoping, and sibling relationships. There is no redundancy or unnecessary detail.

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?

The tool has a single optional parameter and no output schema, and the description covers both execution modes (retrieve a value or list all keys). It also explains the data source (remember) and scoping, making the tool's behavior predictable. Minor omissions like error handling are not critical for this simple memory lookup.

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?

The schema already provides a description for the 'key' parameter with 100% coverage, explaining that omitting it lists all keys. The description enriches this by giving examples of what keys might contain (target ticker, address, research notes) and why they are saved, adding semantic meaning 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 clearly states the tool's dual function: retrieving a previously saved value or listing all keys. It explicitly names companion tools 'remember' and 'forget', distinguishing it from siblings. Concrete examples of stored context make the purpose unmistakable.

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 explicitly tells agents when to use the tool: to look up context stored earlier without re-deriving it. It also advises pairing with 'remember' to save and 'forget' to delete, providing clear guidance on alternatives. The lack of an explicit 'when not to use' is minor given the clear use case.

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

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

Many tools overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, entity_profile, compare_entities, and validate_claim all serve data-lookup purposes with unclear boundaries. The three xkcd comic tools are distinct but are buried under 31 unrelated tools, making selection confusing.

Naming Consistency2/5

Tool names follow no consistent pattern: some use verb_first (get_comic, list_subscriptions), some are nouns (entity_profile, deep_research), some have prefixes (ask_pipeworx_*, polymarket_*), and others are vague (scan_dependency, generate_llms_txt). The mixing of styles across the set makes it hard to predict naming.

Tool Count2/5

With 34 tools and a server name of 'xkcd', the count is wildly disproportionate; only 3 tools relate to comics. Even as a general data-access server, 34 tools is heavy and many are meta-tools (discover_tools, suggest_questions) that add bulk.

Completeness3/5

For the actual Pipeworx data domain, the surface is fairly comprehensive: querying, grounded answers, research, entity profiles, comparisons, validation, subscriptions, and prediction-market analysis are covered. However, there are notable gaps like no fetch-by-URI tool and no xkcd search/list capability, making the set incomplete for its name and slightly incomplete for its inferred domain.

Resources