Skip to main content
Glama

Jisho

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)

TDQS

A4.6/5.0
Behavior5/5

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

Description discloses scoping ('by your identifier'), retention duration (24h anonymous, persistent authenticated), and aligns with annotations (idempotentHint=true, destructiveHint=false). Adds value 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?

Every sentence earns its place: purpose, usage, scope, companion tools. No fluff, well-structured, front-loaded with primary action.

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 write-only tool without output schema, the description covers purpose, usage, parameters, and behavioral context (retention, scoping). Lacks return value info, but acceptable for this type.

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 meaningful examples for keys ('subject_property') and clarifies value is any text, enhancing schema documentation.

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 explicitly states 'Save data the agent will need to reuse later' with a clear verb (save) and resource (key-value memory). It distinguishes from sibling tools like recall and forget by pairing them.

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 clear when-to-use guidance ('when you discover something worth carrying forward') with concrete examples. It also notes pairing with recall/forget, but does not explicitly state when not to use.

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

All Jisho 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.8/5.0
Disambiguation3/5

Most tools have distinct purposes, but there are overlapping tools like the three ask_pipeworx variants (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) and ai_visibility_check/scan_competitor_ai_presence. A few pairs could cause confusion, but overall differentiation is moderate.

Naming Consistency2/5

Tool names follow no consistent pattern: some are imperative verbs (remember, forget), some are compound nouns (entity_profile, polymarket_arbitrage), some are descriptive phrases (recent_alerts, scan_dependency). The verb_noun pattern is absent, leading to inconsistency.

Tool Count1/5

33 tools is far too many for a server named 'Jisho' (a Japanese dictionary), especially since only 2 tools (lookup, search_words) are dictionary-related. The majority of tools belong to an unrelated data platform, making the count wildly inappropriate for the server's apparent purpose.

Completeness3/5

For the dictionary domain, the server lacks common features like example sentences or kanji details. However, the extended tool set covers many data retrieval and analysis tasks, though it is read-heavy with no update/delete capabilities for most resources.

Resources