Skip to main content
Glama

Lens Org

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

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

Description adds context beyond annotations: key-value storage scoped by identifier, persistence differences (authenticated vs anonymous). Annotations already readOnlyHint=false, destructiveHint=false, idempotentHint=true — description aligns and adds detail.

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, front-loaded with purpose. No fluff, each sentence adds value: usage trigger, storage type, persistence details, sibling pairing.

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?

All necessary information is present: purpose, usage, parameters (via schema), persistence, sibling tools. No output schema needed for a write tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline 3. Description provides example keys and values but adds little beyond schema definitions.

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 specific verb 'save' and resource 'data' with clear examples of what to store (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 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... so you don't have to look it up again.' Mentions pairing with recall/forget and scoping differences.

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

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

Multiple tool clusters have unclear boundaries: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are three variants of the same router (beta is currently identical), while bet_research, polymarket_edges, and polymarket_arbitrage all target prediction-market opportunities. ai_visibility_check is effectively a single-entity version of scan_competitor_ai_presence, and discover_tools overlaps heavily with suggest_questions.

Naming Consistency3/5

Tool names are uniformly snake_case and descriptive, but the pattern is mixed: verb-first names (ask_pipeworx, compare_entities, search_within) coexist with noun-first names (patent, scholarly, entity_profile), and the Lens.org pairing of patent/patents_search vs scholarly/scholarly_search is structurally inconsistent. Subgroups like pipeworx_* and polymarket_* are internally consistent, keeping the overall set readable.

Tool Count2/5

At 35 tools, this exceeds the 16-25 'heavy' band and bundles at least four distinct domains: Lens.org bibliometrics, Pipeworx data routing, Polymarket trading analysis, and memory/subscription utilities. While many tools serve legitimate purposes, the set feels sprawling and several variants (e.g., the three ask_pipeworx flavors) inflate the count without adding equivalent value.

Completeness4/5

The Pipeworx/Polymarket ecosystem is thoroughly covered with routing, grounded answers, deep research, entity resolution, validation, comparison, monitoring, and memory all present. The Lens.org portion is thin (search + fetch for patents and scholarly works) but covers the core read path; minor gaps exist such as no batch/export operations and no patent-number lookup.

Resources