Skip to main content
Glama

FiatDock

by com.fiatdock

Search the FiatDock marketplace

search_services
Read-onlyIdempotent

Find paid + free MCP services other agents have published on the FiatDock marketplace. Returns matching listings (id, name, summary, price, category, seller, verified, gatewayUrl). Use get_service for full detail and call_service to invoke one. Read-only, free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree-text relevance search over the listing name, summary, description, tags, category AND the tool names the seller's own MCP server reports (ADR-0067). Multi-word queries are SCORED, not matched literally: results come back best-first, and a listing must carry at least half your words to appear at all
sortNoSort order (default newest; first-party listings are always featured first)
categoryNoFilter by category slug: data, search, finance, dev, productivity, ai, web, other
verifiedOnlyNoOnly verified listings (KYC'd seller or first-party)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of listings returned
servicesYesMatching listings (first-party featured first)

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds the 'free' cost property and clarifies that it returns a summary list rather than full service detail, while matching the read-only annotation. No contradictions or hidden destructive behavior are present.

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

Conciseness5/5

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

The description is four concise sentences with no filler: purpose, return shape, sibling routing, and safety/cost are each covered efficiently. The primary action and result are front-loaded, and every sentence earns its place.

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?

Given the rich input schema, output schema, and annotations, the description covers discovery purpose, result contents, routing to detail/invoke tools, and the read-only/free nature of the operation. Nothing needed to call this zero-required-parameter search tool is missing.

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 the parameter descriptions are already detailed, including q's scoring semantics, sort defaults, and verifiedOnly behavior. The description does not need to repeat this, so the baseline score of 3 is appropriate.

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?

The description states a specific verb and resource: 'Find paid + free MCP services... on the FiatDock marketplace.' It also lists the returned fields and explicitly distinguishes the tool from get_service and call_service, so an agent can tell it apart from its closest siblings.

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?

The description explicitly says 'Use get_service for full detail and call_service to invoke one,' giving clear routing guidance when search results are not enough. This is direct, actionable usage guidance in a tool set where several siblings relate to the same marketplace.

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

All FiatDock toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation4/5

Most tools are clearly separated by resource and action, but a few intentional bundles create mild selection overlap: token_report duplicates the data from token_price + token_safety, and address_intel overlaps eth_balance/usdc_balance plus safety. The descriptions explain the trade-offs well, so this is a minor rather than severe issue.

Naming Consistency4/5

Data-query tools follow a solid subject_metric pattern (token_price, usdc_balance, tx_status), while state-changing tools use verb_object (create_onramp_session, call_service). The pattern is readable and mostly consistent, but not a single uniform verb_noun convention throughout, so it falls just short of perfect.

Tool Count4/5

18 tools is above the typical 3-15 well-scoped range, but the server genuinely spans Base chain primitives, token intelligence, fiat ramps, and a marketplace. Each tool has a purpose, and the count is reasonable rather than bloated.

Completeness4/5

Core workflows are covered end-to-end: quote -> create on/off-ramp session -> order status; token price/safety/metadata/report; marketplace search/get/call; chain/tx primitives. Minor gaps exist, such as no order cancellation, no list-all-services endpoint, and no supported-country/method endpoint despite those details living in descriptions.

Resources