Skip to main content
Glama

Dblp

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

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

Beyond annotations (readOnlyHint, idempotentHint, destructiveHint), the description adds scoping to user identifier and explains the conditional listing behavior. 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 focused sentences with no extraneous information. Core functionality is front-loaded.

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?

Fully covers retrieval and listing behaviors, scoping, and pairing with sibling tools. No output schema needed for this 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 is 100%, so baseline 3. Description adds value by explaining that omitting key triggers listing, which is not fully implied by the schema description alone.

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 begins with the specific verb 'Retrieve' and resource 'saved keys', clearly distinguishing from its siblings 'remember' and 'forget'. It also notes the alternative listing behavior when key is omitted.

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?

It states the tool is used 'to look up context the agent stored earlier' and explicitly names alternative tools ('remember' to save, 'forget' to delete). It lacks explicit when-not scenarios but provides sufficient guidance.

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

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

Many tools overlap in general purpose—ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and validate_claim all retrieve factual data—though their descriptions draw clear mode distinctions. The Polymarket family is similarly dense but each member has a distinct role. An agent must read carefully to pick the right one, but the boundaries are mostly decipherable.

Naming Consistency4/5

Tool names overwhelmingly follow snake_case verb_noun or domain_noun patterns (search_publications, resolve_entity, polymarket_edges, ask_pipeworx). Minor exceptions like the bare verbs recall and forget break the pattern slightly, and mixed prefixes (pipeworx_, ask_, search_) are still predictable.

Tool Count2/5

At 34 tools, the set is heavy, but the deeper problem is scope mismatch: the server is named Dblp yet only 3 of 34 tools (search_authors, search_publications, search_venues) relate to DBLP. The remaining 31 tools form a broad general-purpose data platform that dwarfs and obscures the apparent purpose.

Completeness2/5

For a DBLP server, the surface is minimal: only search operations exist, with no record fetch-by-id, citation metrics, or author profile detail beyond what search returns. The bulk of the toolset addresses unrelated domains, leaving the actual DBLP workflow thin and incomplete.

Resources