Skip to main content
Glama

Pkg Go Dev

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. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "key": "user_research_topic"
+  },
+  {}
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds valuable context about scoping to an identifier and the pairing with remember/forget, enhancing the agent's understanding beyond the 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 serves a purpose: the first states the primary action, the second explains usage, the third details scoping, and the fourth links to sibling tools. No redundancy or unnecessary 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?

Given the simplicity of the tool (one optional parameter, no output schema, clear annotations), the description covers all relevant aspects: purpose, usage context, behavioral traits, and relationship to other tools. No gaps remain.

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?

The input schema describes the 'key' parameter with 100% coverage. The description adds semantic meaning by providing examples of what keys represent (e.g., ticker, address) and explaining the behavior when omitted, which goes beyond the 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?

The description uses specific verbs ('retrieve', 'list') and identifies the resource ('value previously saved via remember', 'all saved keys'). It distinguishes from siblings by naming remember and forget, and clarifies the dual behavior based on argument presence.

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 explicitly states when to use ('to look up context the agent stored earlier') and how it avoids re-deriving information. It mentions scoping and companion tools, but does not explicitly state when not to use the tool.

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

All Pkg Go Dev 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
Disambiguation2/5

Multiple tools have overlapping purposes, such as ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded all performing similar data lookups. Additionally, many tools focus on prediction markets and arbitrage, which are unrelated to the server's implied Go development domain, causing confusion.

Naming Consistency2/5

Tool names follow inconsistent conventions: some use snake_case (e.g., 'latest_version', 'list_versions'), some use underscores in longer names (e.g., 'ai_visibility_check', 'ask_pipeworx_grounded'), and some use colons in descriptions but not in names. This mix reduces predictability.

Tool Count2/5

With 35 tools, the count is high for a server named 'Pkg Go Dev' that only offers a few Go module-related tools (e.g., get_go_mod, list_versions). The majority are unrelated Pipeworx tools, making the scope mismatched and excessive.

Completeness1/5

The tool set severely lacks coverage for Go development tasks. It only includes basic module lookup tools (version listing, mod retrieval) but misses essential operations like dependency analysis, build commands, or testing. The vast majority of tools cover unrelated domains (prediction markets, company profiles, etc.), leaving the server incomplete for its intended purpose.

Resources