Skip to main content
Glama
Sign In

Infrabase

by ai.infrabase
OverviewDiscussionsAdmin

Search AI infrastructure tools

search_tools
Read-onlyIdempotent

Search Infrabase.ai, a hand-verified directory of AI infrastructure products: inference APIs, GPU clouds, vector databases, agent frameworks, observability, gateways and more. Filter by free text, category, job (what the product does) or European headquarters. Returns each product's name, slug, tagline, jobs, pricing model, HQ country, icon and links, plus the total match count. Each result's slug is accepted by get_tool and find_alternatives. CC-BY-4.0. Each result includes an infrabase_url for attribution.

Input Schema

NameRequiredDescriptionDefault
jobNoWhat the product does for a developer, e.g. vector-database, llm-gateway, speech-to-text. Matches primary and secondary jobs.
gdprNotrue: only products that state GDPR compliance
limitNoResults to return, default 20
queryNoFree text search across name, tagline, description and jobs
offsetNoResults to skip, for paging
eu_onlyNoOnly companies headquartered in Europe
categoryNoDirectory category to browse, e.g. vector-databases

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / job / enum
      Previous value: -[
-  "agent-framework",
-  "agent-memory",
-  "agent-payments",
-  "agent-platform",
-  "ai-browser-automation",
-  "ai-search",
-  "decision-model",
-  "embedding-api",
-  "fine-tuning-platform",
-  "gpu-compute",
-  "hosted-inference-api",
-  "image-generation-api",
-  "inference-engine",
-  "llm-evaluation",
-  "llm-gateway",
-  "llm-guardrails",
-  "llm-observability",
-  "llm-orchestration-framework",
-  "local-inference-runtime",
-  "model-hub",
-  "music-generation-api",
-  "prompt-management",
-  "rag-framework",
-  "serverless-gpu-platform",
-  "speech-to-text",
-  "text-to-speech",
-  "vector-database",
-  "video-generation-api",
-  "voice-agent-platform",
-  "workflow-builder"
-]New value: +[
+  "agent-framework",
+  "agent-memory",
+  "agent-payments",
+  "agent-platform",
+  "ai-browser-automation",
+  "ai-search",
+  "decision-model",
+  "embedding-api",
+  "fine-tuning-platform",
+  "gpu-compute",
+  "hosted-inference-api",
+  "image-generation-api",
+  "inference-engine",
+  "llm-evaluation",
+  "llm-gateway",
+  "llm-guardrails",
+  "llm-observability",
+  "llm-orchestration-framework",
+  "llm-router",
+  "local-inference-runtime",
+  "model-hub",
+  "model-lab-api",
+  "music-generation-api",
+  "prompt-management",
+  "rag-framework",
+  "serverless-gpu-platform",
+  "speech-to-text",
+  "text-to-speech",
+  "vector-database",
+  "video-generation-api",
+  "voice-agent-platform",
+  "workflow-builder"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / job / enum
      Previous value: -[
-  "agent-framework",
-  "agent-memory",
-  "agent-platform",
-  "ai-browser-automation",
-  "ai-search",
-  "decision-model",
-  "embedding-api",
-  "fine-tuning-platform",
-  "gpu-compute",
-  "hosted-inference-api",
-  "image-generation-api",
-  "inference-engine",
-  "llm-evaluation",
-  "llm-gateway",
-  "llm-guardrails",
-  "llm-observability",
-  "llm-orchestration-framework",
-  "local-inference-runtime",
-  "model-hub",
-  "music-generation-api",
-  "prompt-management",
-  "rag-framework",
-  "serverless-gpu-platform",
-  "speech-to-text",
-  "text-to-speech",
-  "vector-database",
-  "video-generation-api",
-  "voice-agent-platform",
-  "workflow-builder"
-]New value: +[
+  "agent-framework",
+  "agent-memory",
+  "agent-payments",
+  "agent-platform",
+  "ai-browser-automation",
+  "ai-search",
+  "decision-model",
+  "embedding-api",
+  "fine-tuning-platform",
+  "gpu-compute",
+  "hosted-inference-api",
+  "image-generation-api",
+  "inference-engine",
+  "llm-evaluation",
+  "llm-gateway",
+  "llm-guardrails",
+  "llm-observability",
+  "llm-orchestration-framework",
+  "local-inference-runtime",
+  "model-hub",
+  "music-generation-api",
+  "prompt-management",
+  "rag-framework",
+  "serverless-gpu-platform",
+  "speech-to-text",
+  "text-to-speech",
+  "vector-database",
+  "video-generation-api",
+  "voice-agent-platform",
+  "workflow-builder"
+]
  3. Changed6 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Directory category to browse, e.g. vector-databases"
    • changedInput schema / properties / eu_only / description
      Previous value: -"Scope results to European-headquartered companies"New value: +"Only companies headquartered in Europe"
    • addedInput schema / properties / gdpr / description
      Added value: +"true: only products that state GDPR compliance"
    • addedInput schema / properties / job / description
      Added value: +"What the product does for a developer, e.g. vector-database, llm-gateway, speech-to-text. Matches primary and secondary jobs."
    • addedInput schema / properties / limit / description
      Added value: +"Results to return, default 20"
    • addedInput schema / properties / offset / description
      Added value: +"Results to skip, for paging"
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful non-schema context: the returned field set, the total match count, CC-BY-4.0 licensing, and the attribution requirement tied to infrabase_url.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core purpose and coverage before detailing filters and return fields; no sentence is wasted. It is slightly dense in enumerating domains, but the ordering is appropriate for scanning.

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?

With no output schema, the description usefully enumerates returned fields and the total match count, and covers the slug-to-sibling handoff plus attribution terms. Pagination params exist but their behavior is implied by the schema alone, which is acceptable.

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 coverage is 100% with two enums fully documented inline, so the schema does the heavy lifting. The description restates the filter axes (free text, category, job, EU HQ) but adds no syntax, matching behavior, or interaction rules beyond what the schema already provides.

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?

States a specific verb and resource ('Search Infrabase.ai, a hand-verified directory of AI infrastructure products') and enumerates the domain coverage. It clearly distinguishes itself from siblings like get_tool and find_alternatives by positioning those as downstream consumers of the slugs this tool returns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the filter axes (free text, category, job, European HQ) and explains the search_tools -> get_tool / find_alternatives workflow, which is good routing context. It stops short of explicit when-not guidance or stating which sibling to prefer for other lookup patterns.

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

All Infrabase toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources