New MCP Server Directory (Agent Tools Index)

data_preview

Read-onlyIdempotent

✅ No API key needed. Listing: New MCP Server Directory (Agent Tools Index). Price 0.01 USDC/query (max 20 queries/session). Sample questions: What MCP servers were published today?; Show me new agent tools released this week. FREE preview — no key, no payment. Try one of the sample questions now.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "data_preview"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	No	Public listing slug. Defaults to the routed session's listing when connected via /mcp/data/{slug}/http.
`question`	No	Optional free-text question you'd ask this data (echoed back).

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 6, 2026

TDQS

C2.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered; the description does add useful non-annotation facts (no API key required, max 20 queries/session). However it is internally muddled on cost — 'Price 0.01 USDC/query' immediately followed by 'FREE preview — no key, no payment' leaves the agent unsure whether a charge applies.

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

Conciseness2/5

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

The text is front-loaded with an emoji and repeats the free/no-key message twice while embedding pricing and sample questions. Roughly half the sentences restate 'free, no key' rather than informing tool selection or invocation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 should say what a preview actually returns and how it differs from a paid session result, but it only implies 'sample questions' are answerable. It omits the relationship to data_session_open/fund/query, leaving the agent without the escalation context this tool needs.

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 description coverage is 100% and both optional parameters (slug, question) are documented in the schema, including the 300-char limit and slug routing default. The description adds no parameter meaning beyond listing example questions, so the schema baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the listing ('New MCP Server Directory (Agent Tools Index)') and signals a free 'preview' with sample questions, but it never states the verb plainly — an agent has to infer from the name and the schema description ('guest-callable taste of a listing') that this returns public metadata preview. Marketing framing crowds out a crisp purpose statement.

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

Usage Guidelines2/5

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

'Try one of the sample questions now' encourages use but gives no condition for choosing this over data_session_query, data_session_open, or the other session siblings when a full/paid query is needed. No when-not-to-use guidance and no escalation path after the preview.

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

All New MCP Server Directory (Agent Tools Index) tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?