Skip to main content
Glama

Ocrspace

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)

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds value by explaining scoping (anonymous IP, BYO key hash, account ID) and the behavior of listing all keys when omitted. No contradictions 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.

Conciseness5/5

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

The description is concise, with three well-structured sentences. The main action is front-loaded, and each sentence adds clear value: what it does, when to use it, and how it relates to siblings. No unnecessary 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?

Given the tool's simplicity (1 optional param, no output schema, complete annotations), the description covers all necessary aspects: operation, scoping, and relationship to related tools. It is fully sufficient for an agent to select and invoke correctly.

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 coverage is 100% with a single optional parameter that has a description. The description enhances understanding by explaining that omitting the key lists all keys and providing examples of typical usage (e.g., 'user_research_topic'). This adds 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 clearly states the tool retrieves a value saved via 'remember' or lists all keys when no key is provided. It specifies the resource (saved memory) and the action (retrieve/list), and distinguishes itself from sibling tools like 'remember' 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?

The description provides explicit guidance on when to use the tool—to look up stored context like target ticker or address—and mentions pairing with 'remember' and 'forget'. However, it does not explicitly state when not to use it (e.g., if fresh data is needed), which would strengthen guidance.

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

All Ocrspace 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
Disambiguation2/5

Many tools serve overlapping purposes (multiple ask_pipeworx variants, several entity tools, multiple Polymarket edge tools), and while descriptions are detailed, an agent would struggle to quickly select the correct tool without careful reading.

Naming Consistency2/5

Naming conventions are mixed: some use verb_noun (ask_pipeworx, extract_text), others use noun_phrase (ai_visibility_check, bet_research, entity_profile), and no clear pattern dominates.

Tool Count3/5

32 tools is above the typical well-scoped range (3-15). While the broad domain of data query, prediction markets, memory, and subscriptions somewhat justifies the count, it still feels heavy and could benefit from consolidation.

Completeness4/5

The tool set covers most operations for its domain: data query (with multiple depth levels), memory CRUD, subscription lifecycle, and utilities like OCR and dependency scanning. Minor gaps exist (e.g., no direct modify operation), but overall it's fairly complete.

Resources