Skip to main content
Glama

Pubchem

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

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 indicate idempotentHint=true, destructiveHint=false. Description adds that it stores key-value pairs scoped by identifier and memory duration (24hr for anonymous). 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?

Description is front-loaded with purpose, then usage guidelines, then technical details. Each sentence is necessary and well-organized, 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?

Tool is simple key-value store; description covers persistence, scope, and pairing with siblings. No output schema needed; return value implied by recall. Complete for intended use.

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 has 100% coverage with descriptions. The description adds naming conventions (e.g., 'subject_property') and value content (findings, addresses), providing context 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?

The description clearly states the tool saves data for reuse across conversations, with specific examples (ticker, address, preference). It distinguishes from siblings by mentioning pairings with recall 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?

The description explicitly advises when to use (discover something worth carrying forward) and mentions alternatives (recall to retrieve, forget to delete). It also clarifies persistence based on authentication.

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

All Pubchem 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.6/5.0
Disambiguation2/5

Many tools overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all answer factual questions through similar routing; the polymarket_* tools and entity_profile/compare_entities/recent_changes also cover the same ground. The server is named Pubchem but most tools are unrelated, adding another layer of confusion.

Naming Consistency4/5

All tool names are snake_case and mostly follow verb_noun (search_by_name, get_compound, create_subscription, etc.). Minor deviations exist like entity_profile and recent_alerts being noun-first, and the pipeworx_*/polymarket_* prefixes make the set feel more like multiple products than one coherent API.

Tool Count2/5

35 tools is a large surface, and only 4 (search_by_name, get_compound, get_classification, get_synonyms) actually belong to PubChem. The other 31 tools form a broad Pipeworx/prediction-market toolkit that seems unrelated to the server's stated name and purpose.

Completeness2/5

For a PubChem server the coverage is minimal: basic name->CID resolution, compound properties, classification, and synonyms, but no formula search, bioassay, spectra, or list/search by other identifiers. The Pipeworx tools are extensive for general data querying but require accounts/keys for full use, so anonymous agents hit incomplete workflow dead ends.

Resources