dump_agent_toolsDataset download: $1 USDC via x402. Full dump: Agent Tool Directory, ~13,000 MCP servers + x402 APIs in one unified schema (JSON). MIT + CC BY 4.0 sources, attribution included.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| rows | No | ||
| count | No | ||
| license | No | ||
| sources | No |
Changes observed during successful MCP inspections.
Output schema / descriptionPrevious value: -"Inferred from a real response captured on 2026-10-24; extra fields may appear, null-valued fields are untyped."New value: +"Inferred from a real response captured on 2026-10-26; extra fields may appear, null-valued fields are untyped."Output schema / (root)Previous value: -nullNew value: +{
+ "description": "Inferred from a real response captured on 2026-10-24; extra fields may appear, null-valued fields are untyped.",
+ "properties": {
+ "count": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "license": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "rows": {
+ "items": {
+ "properties": {
+ "category": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "chains": {
+ "type": [
+ "array",
+ "null"
+ ]
+ },
+ "description": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "name": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "price_usd": {},
+ "source": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "status": {},
+ "type": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "url": {
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "sources": {
+ "items": {
+ "properties": {
+ "attribution": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "license": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "name": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "note": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "snapshot": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "url": {
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only and open-world, but the description adds genuinely non-obvious behavior: it costs $1 USDC via x402 and carries MIT/CC BY 4.0 attribution obligations. It stops short of explaining how the x402 payment is actually settled or whether any free preview exists.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three compact fragments with zero waste; the cost, which is the biggest gating fact, is front-loaded in the first sentence. Nothing could be cut without losing a decision-relevant fact.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present and no parameters, the description only needs to cover scope, format, cost, and licensing, and it does all four. Only the mechanics of the x402 payment flow are left unexplained.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Zero parameters, so the schema carries no semantics burden and the baseline applies. The description correctly does not invent parameter details and instead spends its words on scope and cost.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific resource and scope: a full dump of the Agent Tool Directory (~13,000 MCP servers + x402 APIs) in one unified JSON schema. That distinguishes it in spirit from the sample-scoped siblings (mcp_servers_sample, api_directory_sample, dump_llm_pricing), though it never names those siblings explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The word "Full" and the stated scale imply this is the complete dataset rather than a sample, which helps against sample siblings, but the description never says when to pick it over dump_mcp_servers, dump_x402_services, or agent_tools. The $1 price is a useful decision input, yet it is not framed as a trade-off against free alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.