Skip to main content
Glama

Peeringdb

by io.github.pipeworx-io

Search Within a Source

search_within
Read-onlyIdempotent

Semantic search INSIDE a fetched record. Pass the text you already pulled (e.g. a SEC 10-K body, an article, a long tool result) plus a natural-language query; get back the top-N passages with character offsets and similarity scores. Use when the record is too big to cram into the prompt — search_within saves context, returns only the passages that matter, and every passage carries an offset so the agent can verify a verbatim quote. Pairs with ask_pipeworx_grounded: fetch with the gateway, ground over the relevant passages instead of the whole document. BGE-base-en embeddings + cosine over 500-char overlapping windows; cap is 200K chars (longer inputs are truncated and flagged).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe document text to search inside (max ~200K chars).
limitNoMax passages to return (1-20, default 5).
queryYesNatural-language query — what passages do you want? E.g. "supply-chain risk", "fiscal year 2024 revenue", "drug interactions with warfarin".

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 the readOnly/idempotent annotations, the description discloses concrete technical behavior: BGE-base-en embeddings, cosine similarity, 500-char overlapping windows, 200K char cap, and truncation flagging. It also clarifies output includes character offsets and similarity scores, which annotations don't cover.

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 information-dense yet efficient, organizing content into distinct clauses: core function, use case, sibling integration, and technical constraints. No wasted words; every sentence contributes unique value.

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 tool without an output schema, the description explains return values (passages with offsets and similarity scores), constraints (200K cap, truncation flag), and interplay with the gateway tool. It gives enough for an agent to invoke correctly and verify results.

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?

The input schema already documents all three parameters with descriptions, achieving 100% coverage. The description adds contextual meaning by defining 'text' as a fetched record with examples (SEC 10-K, article) and clarifying the query is natural-language, enhancing the schema without repeating it.

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 specifies 'Semantic search INSIDE a fetched record' with a clear verb and resource, and differentiates from siblings by requiring already-pulled text. It explicitly mentions returning top-N passages with offsets and scores, making the tool's function unambiguous.

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 states 'Use when the record is too big to cram into the prompt' and 'saves context, returns only the passages that matter,' providing explicit guidance. It also names the alternative ask_pipeworx_grounded and explains the pairing, offering clear when-not-to-use guidance.

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

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

Many tools overlap in purpose: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and validate_claim all provide data retrieval with subtle differences. The Polymarket suite (arbitrage, edges, edge_tracker, fill_risk, kalshi_spread) and AI visibility tools (ai_visibility_check, scan_competitor_ai_presence) also have fuzzy boundaries. While some tools are clearly distinct, the overall set has significant ambiguity that could lead to misselection.

Naming Consistency2/5

Tool names mix conventions: some are verb_noun (search_networks, compare_entities, remember, forget), others are noun_compound (entity_profile, polymarket_edges, ask_pipeworx), and a few are verb-only (recall, forget). The pattern is inconsistent, with no clear naming strategy across the tool surface.

Tool Count2/5

With 34 tools, the server is heavily overloaded. While it serves as a general data platform, many tools are meta-level (discover_tools, suggest_questions) or peripheral (subscriptions, memory). The count feels excessive for the core purpose, and many tools could be consolidated or removed.

Completeness1/5

Despite the server name 'Peeringdb', only three tools (search_networks, search_facilities, search_exchanges) directly serve that domain. The vast majority of tools cover unrelated areas (Pipeworx data, Polymarket betting, AI visibility, memory, subscriptions). For the declared purpose of PeeringDB, the surface is severely incomplete—missing common operations like retrieving network details, viewing IX members, or managing peering policies.

Resources