Skip to main content
Glama

Jina Reader

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

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

Annotations already indicate idempotentHint=true and non-destructive. Description adds valuable context: memory scoped by identifier, persistent for authenticated users, 24-hour retention for anonymous. 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?

Three sentences, no waste. First sentence establishes purpose, second provides usage guidance, third adds persistence behavior. 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 key-value store with no output schema, the description covers all needed aspects: purpose, when to use, persistence behavior, and relation to siblings. Complete for the tool's complexity.

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

Parameters3/5

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

Schema coverage is 100% with clear descriptions for both key and value parameters. The tool description restates purpose but doesn't add format details beyond the schema. Baseline 3 is appropriate.

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?

Clearly states 'Save data the agent will need to reuse later' specifying action (save), resource (data), and scope (key-value pair, cross-session). Distinguishes from sibling tools recall 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 Guidelines5/5

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

Explicitly tells when to use: 'when you discover something worth carrying forward' and mentions pairing with recall and forget for retrieval/deletion. Also explains scoping and persistence duration for authenticated vs anonymous users.

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

All Jina Reader 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 clearly distinct roles, but there is notable overlap in the ask_pipeworx family (stable, beta, grounded, deep_research), and ask_pipeworx_beta is explicitly described as currently identical to ask_pipeworx. discover_tools and suggest_questions also both serve as meta-guidance, creating some selection ambiguity. The very detailed descriptions help, but they do not fully remove the risk of misselection.

Naming Consistency3/5

The set mixes verb-first names like compare_entities and validate_claim with noun-first names like entity_profile and polymarket_edges, along with prefix families (polymarket_*, pipeworx_*, ask_pipeworx_*) and bare verbs like forget and search. Everything is snake_case and readable, but there is no single predictable convention across the whole surface.

Tool Count2/5

33 tools for a server labeled 'Jina Reader' is a sprawling surface spanning data routing, prediction markets, memory, subscriptions, and web reading. Even if each tool is individually focused, the count and combined scope feel oversized relative to the server name and the rubric's guidance for well-scoped servers.

Completeness4/5

Each sub-domain has good lifecycle coverage: memory (remember/recall/forget), subscriptions (subscribe/unsubscribe/list_subscriptions/recent_alerts), entity research (resolve_entity/entity_profile/compare_entities/recent_changes/validate_claim), and Polymarket analysis (edges/arbitrage/fill_risk/kalshi_spread). There are minor gaps like no order execution or simple page summarization, but those appear intentionally out of scope, leaving the surface largely complete.

Resources