Skip to main content
Glama

iplookup

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. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare write behavior (readOnlyHint false), idempotency, and non-destructiveness. The description adds valuable context beyond annotations: memory is scoped by the agent's identifier, with different persistence for authenticated vs anonymous sessions. This enriches the agent's understanding of side effects.

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 four sentences: first states the core purpose, second gives usage context, third explains storage/scoping, and fourth names companion tools. Every sentence earns its place with no filler or redundancy.

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 two-parameter tool, the description covers the core action, usage timing, persistence behavior, and related tools. Annotations cover safety and idempotency; schema covers parameters. No output schema is necessary for a save operation, so the description is sufficiently complete.

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?

The input schema already provides 100% coverage with clear descriptions for both key and value, including examples. The description reinforces the key-value nature and adds the scoping detail, but doesn't offer additional syntactic or format guidance. Baseline 3 applies since the schema carries the burden.

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 data') and clearly identifies the resource: reusable information stored as a key-value pair. It also distinguishes itself from sibling tools by explicitly pairing with recall and forget, and the title/name are consistent.

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 concrete examples (resolved ticker, target address, user preference). It also names the companion tools for retrieval (recall) and deletion (forget), providing clear alternatives.

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

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

Several tool groups have unclear boundaries: ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, polymarket_edges/arbitrage/bet_research overlap heavily, and scan_competitor_ai_presence merely wraps ai_visibility_check. An agent would frequently have to guess which of several overlapping tools to call.

Naming Consistency3/5

Most tools use lowercase snake_case, but the set mixes verb-first names (resolve_entity, validate_claim) with noun/service-first compounds (polymarket_edges, pipeworx_trending, ai_visibility_check) and inconsistent suffix semantics (ask_pipeworx_beta vs ask_pipeworx_grounded). The pattern is readable but not predictable.

Tool Count2/5

33 tools is far too many for a server named iplookup; only 2 of 33 relate to IP geolocation. The rest form a sprawling data/prediction-market/memory platform that would be better split into multiple focused servers.

Completeness4/5

Within the actual described scope (a Pipeworx data platform), coverage is strong: routed lookups, grounded verification, deep research, entity identity/profile/comparison, claim validation, discovery, subscriptions, memory, feedback, trending, and a full prediction-market arbitrage suite. Minor gaps exist (no direct pack-listing tool, no update for memory values), but there are no critical dead ends.

Resources