Skip to main content
Glama

Opendosm My

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)

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 declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds valuable context about scoping ('Scoped to your identifier - anonymous IP, BYO key hash, or account ID'), which is not present in annotations. 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 front-loaded with the core purpose. Each sentence adds value: the first describes the action, the second gives usage guidance and examples, the third covers scoping and related tools. No wasted words.

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 read tool with one optional parameter and no output schema, the description covers purpose, usage, scoping, and relationship to siblings. Annotations handle safety. No gaps remain for the agent to misinterpret.

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 a single optional 'key' parameter. Description clarifies that omitting the key lists all saved keys, adding behavioral insight beyond the schema's description. Examples in the schema ('user_research_topic') are supplemented by the description's concrete examples (ticker, address, notes).

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 main action: 'Retrieve a value previously saved via remember, or list all saved keys (omit the key argument).' It includes the verb 'retrieve'/'list' and the resource 'values/keys', and distinguishes from siblings by mentioning pairing with remember 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 states when to use the tool: 'Use to look up context the agent stored earlier...' and provides examples of use cases (ticker, address, notes). It also notes the alternative of omitting the key to list all keys and mentions sibling tools (remember, forget) for complementary operations.

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

All Opendosm My 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

A4.1/5.0
Disambiguation3/5

The set includes three nearly-identical ask_pipeworx variants (base, beta, grounded) that differ only subtly, and deep_research overlaps with ask_pipeworx for multi-part queries. Several company/prediction tools also share adjacent purposes (entity_profile vs recent_changes vs compare_entities; polymarket_arbitrage vs polymarket_edges), though detailed descriptions help. Overall, an agent could mis-select between these overlapping tools.

Naming Consistency4/5

Most tools follow a verb_noun or consistent prefix pattern (opendosm_*, polymarket_*), and the ask_pipeworx family is internally consistent. However, a few are noun phrases (entity_profile, ai_visibility_check, recent_alerts) and some verbs aren't uniform (list_datasets vs dataset_meta vs get_dataset). The mixture is readable but not fully consistent.

Tool Count2/5

34 tools is well above the typical focused server range and includes a clearly redundant experimental variant (ask_pipeworx_beta) plus many loosely-related utility functions (memory, subscriptions, dependency scanning, llms.txt generation). While the broad scope justifies some size, the count feels excessive for the 'Opendosm My' name, which suggests a narrower Malaysian-statistics focus.

Completeness4/5

For the apparent overarching goal of a multi-domain research/query platform, the surface is quite complete: data lookup, deep research, entity comparison, claim verification, prediction-market analysis, memory, and subscriptions are all covered. The Malaysian OpenDOSM component itself has list/meta/get lifecycle. Minor gaps (e.g., no direct dataset search beyond curated lists, no way to execute arbitrary Pipeworx tools directly) are workable.

Resources