dataset_fullDataset download: $1 USDC via x402. Buy the full Verified API Directory dataset (2,230 rows, JSON, CC BY 4.0 + MIT sources) in one call.
| 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": {
+ "alive": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "auth": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "category": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "checked_at": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "cors": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "description": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "free_tier_details": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "http_status": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "https": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "kind": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "name": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "url": {
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "sources": {
+ "items": {
+ "properties": {
+ "license": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "name": {
+ "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 only declare readOnlyHint and openWorldHint, while the description adds critical behavioral context: the tool requires a $1 USDC payment via x402. It also discloses dataset size and licensing, which helps set expectations. It does not explain the payment flow or whether payment is automatic, but the key cost and access condition are surfaced.
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?
Two compact sentences that front-load the core action and cost, then add dataset specifics. Every phrase earns its place with no redundancy.
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?
The tool is a simple parameterless download with an output schema, so the description need not explain return values. It covers cost, dataset scope, format, and licensing, which is enough to call it correctly. A brief note on how x402 payment is handled would make it complete, but the essential context is present.
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?
The tool has zero parameters, so the schema offers no parameter semantics to document. The baseline for a parameterless tool is 4, and the description appropriately does not invent parameter details.
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?
The description uses a specific verb ('Buy') and resource ('full Verified API Directory dataset'), and explicitly distinguishes it from a sample by the word 'full'. It adds concrete details (2,230 rows, JSON, licenses), so an agent can immediately tell what it retrieves.
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 description implies when to use it (when you need the complete dataset) but does not explicitly name an alternative like api_directory_sample or state when not to use this tool. Usage is therefore inferred rather than directed.
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.