Skip to main content
Glama

Realestate

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

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

Beyond annotations (which indicate a write operation with idempotency and no destructiveness), the description discloses scoping by identifier, persistence duration (24 hours for anonymous, permanent for authenticated), and that it stores key-value pairs.

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?

Three sentences, each serving a clear purpose: stating the function, giving usage guidance, and detailing behavior. No redundant 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?

For a two-parameter tool with no output schema, the description covers purpose, usage, persistence, and pairing with siblings. It fully addresses the agent's needs for correct invocation.

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 descriptions. The description adds value by providing concrete examples for the key parameter and clarifying the value as 'any text', which aids understanding 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 ('Save') and resource ('data'), and clearly states the scope ('across this conversation or across sessions'). It distinguishes from sibling tools by naming '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 says when to use: 'when you discover something worth carrying forward'. It also provides context for when not to overuse by implying it's for persistent storage, and mentions alternative tools ('recall', 'forget').

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

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

Multiple tools occupy the same natural-language lookup niche: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and validate_claim all answer factual questions, and the beta tool is currently described as identical to the stable router. Prediction-market edge detection also fans out across bet_research, polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, and polymarket_fill_risk, so an agent can easily select the wrong one.

Naming Consistency4/5

Most names follow a predictable snake_case action-first pattern (ask_pipeworx, resolve_entity, subscribe, unsubscribe) with helpful domain prefixes for polymarket_*, realestate_*, and pipeworx_*. Minor deviations exist—entity_profile is noun-first, ask_pipeworx lacks an underscore, and remember/forget/recall are bare verbs—but they do not create real confusion.

Tool Count2/5

33 tools is well above the coherence sweet spot and the rubric's 25+ threshold. The count is inflated by auxiliary platform utilities (feedback, trending, memory, subscriptions, llms.txt generation, npm scanning) that are unrelated to the Realestate name and make the tool surface feel like a full platform rather than a focused MCP server.

Completeness2/5

For a server named Realestate, the surface is only minimally complete: realestate_municipalities and realestate_transactions cover Japanese transaction lookups, but there are no tools for property listings, property details, pricing estimates, or typical real-estate workflows. Even viewed as a broad data platform, the set is read-heavy with no create/update/delete operations beyond memories and subscriptions, leaving significant workflow gaps.

Resources