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)

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

The server name 'Shodan' misleadingly implies a narrow focus on network security scanning, yet the tool set includes many unrelated tools for data lookup (ask_pipeworx, deep_research, etc.), memory management, and subscriptions. Within the pipeworx tools, there is overlap between ask_pipeworx, ask_pipeworx_grounded, and deep_research, which can confuse agents about which to choose.

Naming Consistency2/5

Tool names mix conventions: some use underscores (ai_visibility_check, shodan_host), others use lowercased phrases without clear partitioning (ask_pipeworx, deep_research, entity_profile). Verb-noun patterns are inconsistent (e.g., 'scan_competitor_ai_presence' vs 'compare_entities'). This lack of a predictable naming scheme increases cognitive load.

Tool Count2/5

With 33 tools covering distinct domains (Shodan scanning, pipeworx data, memory, subscriptions), the server feels overloaded and unfocused. While each tool may individually be useful, the bundling contradicts the principle of a single-purpose server. A more appropriate count for a focused Shodan server would be under 10 tools.

Completeness2/5

For the Shodan domain, only three tools are provided (host, host_count, host_search), missing key capabilities like DNS lookups, vulnerability search, or API key management. The pipeworx tool set is extensive but not the server's advertised purpose, leaving gaps in both areas. The addition of memory and subscription tools adds unrelated functionality without completing any single domain.

Resources