Skip to main content
Glama

Osv

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. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds valuable context like scoping ('anonymous IP, BYO key hash, or account ID') and the ability to list all keys by omitting the argument, which goes beyond what annotations provide.

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?

Four sentences, each earning its place: action, usage examples, scoping, pairing with siblings. Front-loaded with the most critical information, no wasted words.

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 the tool's simplicity, the description covers the typical use cases. It explains the main actions (retrieve value or list keys), scoping, and relationships. Lack of output schema is mitigated by the straightforward nature. Could mention error handling (e.g., key not found) 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?

The input schema already covers the parameter with a description. The description reinforces the behavior (omit to list all keys) and gives an example key value ('user_research_topic'), adding practical meaning beyond the 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 uses a specific verb ('Retrieve' or 'list') and resource ('value previously saved via remember' or 'all saved keys'). It clearly distinguishes the tool's core actions and ties to sibling tools like 'remember' and 'forget', making the purpose unambiguous.

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?

The description provides concrete usage scenarios ('the user's target ticker, an address, prior research notes') and explicitly pairs with 'remember' and 'forget', implying when to use. It lacks explicit exclusions (e.g., when not to use, or alternatives among siblings) but is clear enough for practical use.

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

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

A4/5.0
Disambiguation3/5

Several tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are very similar, as are the suite of polymarket_* tools. While descriptions help differentiate, an agent may struggle to choose the correct one without careful reading.

Naming Consistency3/5

All tool names use snake_case, but they mix verb-first patterns (ask_pipeworx, compare_entities, validate_claim) with noun-first patterns (bet_research, entity_profile, pipeworx_feedback). This inconsistency makes it harder to guess tool names by convention.

Tool Count3/5

35 tools is on the high side but not unreasonable for a platform covering vulnerability queries, data retrieval, prediction markets, and utilities. However, the server name 'Osv' suggests a narrow focus, making the large count feel bloated.

Completeness4/5

The tool set covers a wide range of operations: querying data, comparing entities, managing user data, monitoring subscriptions, and even onboarding. Minor gaps exist (e.g., no direct API for updating user profiles), but overall it is well-rounded for its domain.

Resources