Skip to main content
Glama

Sciencebase

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)

TDQS

A4.4/5.0
Behavior4/5

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

Adds key-value storage, scoping by identifier, persistence details (authenticated vs anonymous). Annotations already provide idempotency and non-destructive hints; description enriches without contradiction.

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?

Concise, front-loaded with purpose, then usage, then details. Every sentence adds value.

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?

Given no output schema, description adequately covers behavior, persistence, pairing. Could mention return value or confirmation, but not critical.

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 parameters with descriptions; description adds clarifying examples and notes that value is any text. No enums or nested objects needed.

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?

Description clearly states the tool saves data for later reuse, with specific examples (ticker, address, preference). Distinguishes from siblings 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly advises use when discovering something worth carrying forward. Mentions pairing with recall and forget. Could add when not to use, but context is sufficient.

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

All Sciencebase 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.9/5.0
Disambiguation4/5

Most tools have distinctly described purposes, but there is some overlap among query tools like ask_pipeworx, ask_pipeworx_grounded, deep_research, and validate_claim, which could cause confusion for an agent.

Naming Consistency3/5

Tool names are consistently snake_case but vary in pattern: some are verb_noun (ask_pipeworx, compare_entities), while others are noun_noun (entity_profile, polymarket_arbitrage) or longer phrases (scan_competitor_ai_presence), making the naming system inconsistent.

Tool Count2/5

With 33 tools, the server feels over-scoped. Many tools are niche (e.g., polymarket-specific ones) and the high number exceeds the typical range for a focused server, leading to potential overwhelm.

Completeness3/5

The server covers a broad range of query and monitoring tasks for its domains, but lacks write operations (except memory tools). There are notable gaps like no tool for creating or editing ScienceBase items, which seems incomplete given the server's name.

Resources