Skip to main content
Glama

Hgnc

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

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

Annotations indicate read-only, non-destructive, idempotent behavior. Description adds scoping detail (by identifier) and confirms retrieval action, which aligns with 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 concise sentences with the core action front-loaded. Every sentence adds value: retrieval action, usage examples, scoping, and pairing with siblings.

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

Completeness4/5

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

Adequately covers the tool's behavior given its simplicity, annotations, and single parameter. No output schema needed; the purpose and scope are clear.

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 covers 100% of the single optional parameter. Description adds the crucial detail that omitting the key lists all saved keys, which is not in the schema description.

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 it retrieves a saved value by key or lists all keys if omitted. Distinguishes from sibling tools remember and forget by using specific verbs and mentioning pairing.

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 describes when to use: to look up previously stored context without re-deriving. Mentions pairing with remember and forget, but does not state when not to use it.

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

All Hgnc 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

Tools are mostly distinct but several ask_pipeworx variants and research tools overlap in purpose, which could lead to agent confusion. The presence of memory and subscription tools adds unrelated functionality.

Naming Consistency2/5

Naming is inconsistent, mixing snake_case with varying verb patterns (ask, get, search, scan, etc.) and no clear convention. Some tools have descriptive phrases (e.g., generate_llms_txt) further breaking consistency.

Tool Count2/5

34 tools is excessive for a coherent server, covering too many disparate domains (genes, data queries, betting, memory) without clear focus. A gene server should have far fewer tools.

Completeness3/5

Gene-related tools are complete for basic queries (search, get, resolve), but the server's main purpose (HGNC) is overshadowed by many unrelated Pipeworx tools, creating a mismatch. The overall surface is broad but lacks domain focus.

Resources