Skip to main content
Glama

Entur

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

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

Annotations (readOnlyHint, idempotentHint, destructiveHint) already cover basic behavior. Description adds valuable context: scoping to identifier and the omitting-key behavior for listing all keys, which are not in 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?

Two sentences, no wasted words. Purpose is front-loaded. Examples embedded naturally. Efficient and clear.

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 parameter, no output schema, and comprehensive annotations, the description fully covers purpose, usage, and behavioral nuances. No gaps apparent.

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 a clear description of the optional 'key' parameter. The tool description repeats the behavior of omitting the key to list all keys, adding little new to what schema already provides, so 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?

Clear verb ('Retrieve', 'list') and resource ('value previously saved via remember', 'all saved keys'). Distinguishes from siblings (remember, forget) by explicitly stating it pairs with 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?

Explicitly states when to use: 'look up context the agent stored earlier... without re-deriving it from scratch'. Mentions scoping and pairing with remember/forget, but does not provide explicit when-not-to-use or alternatives beyond the sibling context.

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

All Entur 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.7/5.0
Disambiguation2/5

Although many tools are individually well-described, there are several overlapping clusters: three ask_pipeworx variants, multiple polymarket edge/arbitrage tools, and AI-visibility checks vs their competitor-comparison wrapper. An agent can easily pick the wrong one because the boundaries (beta vs stable, grounded vs routed, edge vs arbitrage) are subtle despite the verbose descriptions.

Naming Consistency3/5

The set is consistently snake_case and mostly readable, so naming is not chaotic. However, the pattern is mixed: some tools use entur_/polymarket_/pipeworx_ prefixes, others are bare verbs (remember, recall, forget), and some are noun phrases (entity_profile, pipeworx_trending). The ask_pipeworx family also doesn't follow the pipeworx_ prefix convention used by neighboring tools.

Tool Count2/5

34 tools is well past the healthy range for a focused MCP server, and only three tools relate to the Entur transport domain implied by the server name. The other 31 tools form a separate, broad data/prediction-market product that appears bolted on, making the count inappropriate for the apparent purpose.

Completeness2/5

The Entur transport subset has stops search, departures, and journey planning, but misses common public-transport needs such as disruptions, service alerts, and fare/ticket information. The broader tool set is extensive but lacks a single coherent domain to be complete against, leaving the overall surface scattered and hard to trust as an integrated whole.

Resources