Skip to main content
Glama

Osrm

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?

Description adds scoping detail (anonymous IP, BYO key hash, account ID) beyond annotations. No contradictions with 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 efficient sentences with front-loaded main action. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers usage, scoping, and sibling pairing. Lacks description of return format (string or list) but acceptable for simple tool.

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 100%, baseline 3. Description explains that omitting key lists all saved keys, adding practical nuance beyond 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?

Description clearly states it retrieves a saved value or lists all keys. Distinguishes from siblings 'remember' and 'forget' by mentioning them explicitly.

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?

States when to use (look up context stored earlier) and how to list all keys (omit argument). Does not explicitly exclude cases but pairs with siblings for completeness.

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

All Osrm 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.4/5.0
Disambiguation3/5

Many tools have distinct purposes, but there is notable overlap between ask_pipeworx, ask_pipeworx_grounded, and deep_research, all serving data retrieval. Similarly, the Polymarket betting tools (bet_research, polymarket_arbitrage, polymarket_edges, etc.) share a domain, causing potential confusion for an agent.

Naming Consistency2/5

Tool names follow no consistent pattern: snake_case (ai_visibility_check), camelCase-like (bet_research, compare_entities), and noun-first (entity_profile, recent_changes) are mixed. The lack of a uniform verb_noun or other convention makes it harder to predict tool names.

Tool Count2/5

35 tools is excessive for a server named 'Osrm,' which suggests a focused routing engine. The actual tool set spans routing, data query, betting, entity resolution, and memory, indicating an overbroad scope that dilutes coherence.

Completeness3/5

The data query and betting tools are relatively comprehensive, but the routing side is minimal (missing isochrones, alternative routes). Gaps exist in general web search and coverage of other prediction markets. The server doesn't fully cover either the implied routing domain or the broader data/betting domain.

Resources