Skip to main content
Glama

Osf

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

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

Adds beyond-annotation context: scoping by identifier, persistence differences (auth vs anonymous), and 24-hour retention. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Reasonably concise with front-loaded purpose; every sentence adds value, though could be slightly tighter.

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?

For a simple write tool with 2 params and no output schema, the description covers scope, usage, persistence, and lifecycle completely.

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 parameters with descriptions; description adds naming conventions and value examples, enhancing understanding 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?

Description uses a specific verb ('Save') and resource ('data...key-value pair'), and contrasts with siblings ('recall', 'forget'), making the tool's distinct purpose very clear.

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?

Explicitly states when to use ('when you discover something worth carrying forward'), provides examples, and mentions complementary tools ('Pair with recall...forget'), giving clear usage guidance.

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

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

Several tools have near-identical or heavily overlapping purposes: ask_pipeworx and ask_pipeworx_beta are currently identical, ask_pipeworx and validate_claim both answer factual questions, and discover_tools and suggest_questions both surface capabilities. The dense set of Polymarket and entity-research tools further blurs boundaries despite long descriptions.

Naming Consistency3/5

Names are consistently snake_case, but they do not follow a single predictable verb_noun pattern: actionable names like ask_pipeworx, search_projects, and compare_entities mix with noun-style names like polymarket_edges, pipeworx_feedback, and recent_changes. The convention is readable but not uniform.

Tool Count2/5

34 tools exceeds the reasonable scope for a coherent server, and many are near-duplicate variants or members of sprawling tool families (ask_pipeworx variants, multiple Polymarket scanners, several meta/discovery tools). The set would be stronger with consolidation around a smaller number of distinct capabilities.

Completeness1/5

If this server is meant to provide OSF access, the surface is severely incomplete: only search_projects, search_preprints, and get_project exist, with no create/update/delete, file handling, registration, or contributor access. If it is meant to be a broader Pipeworx assistant, the OSF tools are unrelated and the domain is so scattered that coverage is incoherent.

Resources