Skip to main content
Glama

Agentropolis

by io.agentropolis
OverviewDiscussionsAdmin

Search tools, paid APIs and MCP servers by task

search_kits
Read-onlyIdempotent

Search the Agentropolis index of 48,190 agent-usable listings (MCP servers, x402/MPP pay-per-call HTTP APIs, A2A agents and kits) by task keywords, with optional filters. Use it first when you need a tool for a task; then use get_kit for one listing's trust evidence and price, or get_kit_manifest for how to call it. Not for browsing categories (list_categories) or market totals (get_market_snapshot). Read-only, no auth, never pays. Ranking: BM25 text relevance, boosted by payment-verified trust and the earned Live-Tested badge; trust.score null means no payment evidence (not a negative signal). results[] is organic; featured[] is a separate, labelled Agentropolis Pro row (today only our own first-party kits, no fee paid) and sponsored[] is always empty. Listed prices are hints; the seller's live HTTP 402 challenge is authoritative. Each search is logged anonymously (query text, no raw IP). Example: {"q":"web search","rail":"x402","max_price_usd":0.01,"min_trust":40}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesWhat the agent needs, in plain words: 'web search', 'transcribe audio with speakers', 'postgres', 'token honeypot check'. Keywords beat full sentences.
kindNoRestrict to one listing type: kit (packaged task API), http_api (pay-per-call HTTP API), mcp_server, a2a_agent. Omit for all.
railNoOnly listings that accept this payment rail: x402 (USDC on-chain, per call) or mpp (Machine Payments Protocol).
limitNoNumber of organic results to return, 1-25 (default 10).
categoryNoCategory id from list_categories, e.g. 'web_search' or 'crypto_onchain_data'. Comma-separate to allow several.
min_trustNoOnly listings with a payment-verified trust score of at least this value (0-100). Excludes listings with no payment evidence.
paid_onlyNotrue = only listings that accept a payment rail (x402 or MPP).
max_price_usdNoOnly listings whose lowest listed price per call/unit is at most this many US dollars, e.g. 0.01. Listings without a known price are excluded when set.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYesOrganic matches before limit
rankingYesHow results were ranked
resultsYesOrganic results: id, name, kind, summary, pricing, trust, badges, tiers, invoke, links (page, kit_manifest, call when relayable, go), buy (relay_x402 or link_out)
featuredYesLabelled Agentropolis Pro row, separate from organic results
search_idNoAnonymous id for this search
sponsoredYesAlways empty today
featured_labelYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Category id from list_categories, e.g. 'web_search' or 'crypto_onchain_data'. Comma-separate to allow several."
    • addedInput schema / properties / kind / description
      Added value: +"Restrict to one listing type: kit (packaged task API), http_api (pay-per-call HTTP API), mcp_server, a2a_agent. Omit for all."
    • addedInput schema / properties / limit / description
      Added value: +"Number of organic results to return, 1-25 (default 10)."
    • addedInput schema / properties / max_price_usd / description
      Added value: +"Only listings whose lowest listed price per call/unit is at most this many US dollars, e.g. 0.01. Listings without a known price are excluded when set."
    • addedInput schema / properties / max_price_usd / minimum
      Added value: +0
    • addedInput schema / properties / min_trust / description
      Added value: +"Only listings with a payment-verified trust score of at least this value (0-100). Excludes listings with no payment evidence."
    • addedInput schema / properties / paid_only / description
      Added value: +"true = only listings that accept a payment rail (x402 or MPP)."
    • changedInput schema / properties / q / description
      Previous value: -"What the agent needs, e.g. 'web search', 'sales pitch', 'image generation'"New value: +"What the agent needs, in plain words: 'web search', 'transcribe audio with speakers', 'postgres', 'token honeypot check'. Keywords beat full sentences."
    • addedInput schema / properties / q / maxLength
      Added value: +200
    • addedInput schema / properties / q / minLength
      Added value: +1
    • addedInput schema / properties / rail / description
      Added value: +"Only listings that accept this payment rail: x402 (USDC on-chain, per call) or mpp (Machine Payments Protocol)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "featured": {
+      "description": "Labelled Agentropolis Pro row, separate from organic results",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "id": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "featured_label": {
+      "type": "string"
+    },
+    "ranking": {
+      "description": "How results were ranked",
+      "type": "string"
+    },
+    "results": {
+      "description": "Organic results: id, name, kind, summary, pricing, trust, badges, tiers, invoke, links (page, kit_manifest, call when relayable, go), buy (relay_x402 or link_out)",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "kind": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "kind"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "search_id": {
+      "description": "Anonymous id for this search",
+      "type": "string"
+    },
+    "sponsored": {
+      "description": "Always empty today",
+      "items": {},
+      "type": "array"
+    },
+    "total": {
+      "description": "Organic matches before limit",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "results",
+    "featured",
+    "featured_label",
+    "sponsored",
+    "ranking"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnly/idempotent/non-destructive), it discloses no-auth, never-pays, anonymous query logging, BM25 ranking boosted by payment-verified trust and Live-Tested badges, the meaning of trust.score null, the results/featured/sponsored array structure, and that listed prices are hints while the seller's 402 challenge is authoritative. This is unusually rich behavioral context.

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-loaded with the purpose and routing guidance, and nearly every sentence carries non-redundant information (safety, ranking, result-array shape, price caveat, logging, example). It is on the long side and the featured/sponsored sentence is somewhat dense, but the length is justified by the number of behaviors disclosed.

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 discovery endpoint, the description covers query intent, filters, ranking, result partitions, trust semantics, price caveats and privacy logging. An output schema exists, yet the description still gives the agent enough to interpret and act on results without gaps.

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?

Schema description coverage is 100%, so the baseline is 3; the description still adds meaning beyond the schema, e.g. that trust.score null means no payment evidence (not negative) and that listed prices are hints vs the live HTTP 402 challenge, plus a worked query example.

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 (Search) and resource (the Agentropolis index of 48,190 agent-usable listings), enumerating what is indexed (MCP servers, x402/MPP APIs, A2A agents, kits). It explicitly differentiates itself from siblings like get_kit, get_kit_manifest, list_categories and get_market_snapshot.

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?

Gives explicit ordering guidance ('Use it first when you need a tool for a task; then use get_kit ... or get_kit_manifest') and names when-not-to-use it ('Not for browsing categories (list_categories) or market totals (get_market_snapshot)'). Alternatives and their selecting conditions are spelled out.

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

All Agentropolis toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources