Skip to main content
Glama

Property Records

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

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds valuable context beyond that: key-value scoping by identifier, persistence behavior (authenticated vs anonymous 24h retention), and pairing with recall/forget. 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 three sentences, front-loaded with the core purpose, and every sentence adds value: purpose, usage, storage behavior, persistence details, and sibling relationships. No fluff or repetition.

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 2-parameter write tool with no output schema, the description covers purpose, usage, retention, scoping, and related tools. It is complete for an agent to select and use the tool correctly.

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 description coverage is 100%, and both parameters are well-documented with examples. The description does not add additional parameter-specific meaning beyond what the schema already provides, so baseline 3 is appropriate.

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+resource ('Save data') and clearly distinguishes from sibling tools by naming recall and forget as complementary actions. It also provides concrete examples of use cases (ticker, address, preference) that make the purpose instantly 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?

The description explicitly states when to use the tool ('Use when you discover something worth carrying forward') and gives examples. It also names alternatives/complements (recall, forget), satisfying the when/alternatives criterion.

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

All Property Records 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.6/5.0
Disambiguation2/5

Multiple tools overlap heavily: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical variants of the same router, and there are six polymarket-related tools with overlapping arb/edge/fill-risk purposes. Property-specific tools are distinct but buried among many unrelated meta-tools.

Naming Consistency3/5

All names use snake_case, but the structural pattern is inconsistent: some are verb_noun (ask_pipeworx, validate_claim), others noun_verb (property_lookup), and many are noun_noun (entity_profile, polymarket_arbitrage). No clear systematic convention across the set.

Tool Count2/5

33 tools is far too many for a server labeled 'Property Records'—only two tools (property_lookup, property_coverage) actually serve that purpose. The rest belong to unrelated domains (general data lookup, prediction markets, memory, subscriptions), making the surface feel bloated and unfocused.

Completeness2/5

For a property-records server, the surface is incomplete: it only provides lookup plus a coverage matrix, with no other property-related operations (e.g., tax history, comparable sales) and no way to handle unsupported jurisdictions beyond a simple flag. The unrelated tools do not contribute to the stated domain, leaving the core purpose thinly covered.

Resources