Skip to main content
Glama

Shodan

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

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

Annotations provide idempotentHint=true, but description adds valuable context: persistence differences between authenticated vs anonymous users, and scoping by identifier. No contradictions.

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 wasted words. Each sentence adds distinct value: purpose, usage, format, and pairing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema is needed for a simple save operation. Description covers key behavioral aspects (persistence, scope, pairing) sufficiently for an agent to use 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 covers both parameters fully (100% coverage). Description adds example key formats and notes value is 'any text', which is helpful but not essential beyond 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 verb 'Save data' and resource 'memory key-value pair', with specific examples (ticker, address, preference) that distinguish it 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 says when to use: 'when you discover something worth carrying forward' and provides alternatives: recall to retrieve, forget to delete. Also clarifies scoping and persistence.

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

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

Several tool families have unclear boundaries: ask_pipeworx_beta is explicitly identical to ask_pipeworx right now, ask_pipeworx_grounded and validate_claim both verify claims against sources, and polymarket_edges/polymarket_arbitrage/bet_research all surface prediction-market opportunities. Agents would need to read very long descriptions to distinguish overlapping intents, and would likely misroute requests.

Naming Consistency3/5

All names use snake_case, which is a consistent base, and subgroups (shodan_host*, ask_pipeworx*, polymarket_*) follow internal patterns. However, conventions mix verb-first (ask_pipeworx, validate_claim, resolve_entity) with noun-first (entity_profile, bet_research, recent_alerts), and parallel functionality is named with inverted ordering (ai_visibility_check vs scan_competitor_ai_presence).

Tool Count2/5

34 tools is above the comfortable range for a single server and the breadth feels bloated, especially with five highly niche Polymarket tools. More critically, the server is named 'Shodan' but only 3 of 34 tools are Shodan-related, so the count is badly mismatched with the stated identity.

Completeness2/5

For a server claiming to be Shodan, the surface is severely incomplete — only host lookup, search, and count are present, with no DNS, alerting, or other standard Shodan operations. For the actual Pipeworx/Polymarket domain implied by most tools, coverage is fuller but still has gaps such as no direct tool to fetch a pipeworx:// citation URI, and the memory/subscription features feel bolted on rather than integral.

Resources