Skip to main content
Glama

Wiktionary

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)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already provide idempotentHint=true, indicating repeated calls have the same effect. The description adds valuable behavioral context such as persistence duration (24 hours for anonymous, persistent for authenticated) and scoping by identifier, which goes 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?

Three tightly packed sentences with no wasted words. The first sentence states the core purpose, the second provides usage guidance, and the third adds behavioral details. Perfectly front-loaded and structured.

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 only two required parameters and no output schema or nested objects, the description covers all essential aspects: purpose, usage, pairing, scoping, and retention. No gaps remain.

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% with descriptions for both parameters. The description adds usage examples for the key ('subject_property', 'target_ticker') and clarifies that value is any text, enhancing the 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 saves data for later reuse, using specific verbs like 'save' and 'store', and distinguishes itself from the related tools 'recall' and 'forget' that are listed as siblings.

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 states when to use ('when you discover something worth carrying forward'), provides context on scoping and retention (authenticated vs anonymous), and mentions the complementary tools 'recall' and 'forget'.

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

All Wiktionary 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.1/5.0
Disambiguation1/5

The toolset is overwhelmingly fragmented: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical entry points; polymarket_edges, polymarket_arbitrage, and polymarket_fill_risk heavily overlap; and ai_visibility_check vs scan_competitor_ai_presence cover the same task. The five actual Wiktionary tools are distinct but are lost among dozens of unrelated research and prediction-market tools, making selection highly ambiguous.

Naming Consistency3/5

All names use snake_case and several logical prefixes (ask_pipeworx, polymarket_, pipeworx_) create local patterns. However, the naming mixes noun-style commands (definition, etymology, pronunciations, summary) with verb-style commands (search, remember, forget, validate_claim), and no consistent verb_noun convention carries across the whole set.

Tool Count1/5

36 tools is already heavy, but the deeper problem is that only 5 tools actually belong to a Wiktionary server while 31 tools serve unrelated Pipeworx, Polymarket, memory, and marketing-audit functions. The count is wildly inappropriate for the declared server purpose.

Completeness2/5

The Wiktionary-relevant tools cover basic word lookup—search, summary, definition, etymology, pronunciations—but omit common dictionary operations like translations, usage examples, inflected forms, or random entries. The non-Wiktionary majority does not fill these gaps; it just makes the surface area incoherent and hard to reason about.

Resources