FREE. Search the currently published SYNTHORA tools by keyword and optional USDC price ceiling. Returns tool name, advertised price and example arguments. Only the live catalog is searched; a match is not proof of paid delivery or data freshness. Start here to choose a tool.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | keywords in currently published tool names or descriptions | |
| max_price_usdc | No | optional USDC price ceiling |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "max_price_usdc": 0.03,
+ "query": "bitcoin fees"
+ }
+]Input schema / properties / max_price_usdc / descriptionPrevious value: -"optional price ceiling"New value: +"optional USDC price ceiling"Input schema / properties / max_price_usdc / minimumAdded value: +0Input schema / properties / query / descriptionPrevious value: -"keywords, e.g. 'sanctions', 'nft', 'exchange rates'"New value: +"keywords in currently published tool names or descriptions"Input schema / properties / query / examplesAdded value: +[
+ "bitcoin fees",
+ "exchange rates"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only, idempotent and closed-world behavior, and the description adds genuinely new context: the call is free, only the live catalog is searched, and a match is 'not proof of paid delivery or data freshness'. That honesty about result trustworthiness is valuable. It stops short of describing rate limits or result ordering.
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?
Four short sentences, each earning its place, with the most decision-relevant fact ('FREE') front-loaded and the routing hint ('Start here') at the end. No filler or 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?
With no output schema, the description carries the return burden and does so by naming the returned fields (tool name, advertised price, example arguments) and the catalog-scope caveat. An agent has everything needed to decide to call it and to interpret results.
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?
Schema description coverage is 100%, so both parameters are already documented in the schema. The description restates them (keyword, optional price ceiling) without adding matching semantics or format detail beyond what the schema provides, so the baseline 3 applies.
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 verb and resource ('Search the currently published SYNTHORA tools') plus the search dimensions (keyword, USDC price ceiling) and the return shape. This is clearly distinguishable from all sibling tools, which are concrete data endpoints rather than a catalog lookup.
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?
'Start here to choose a tool' gives an explicit entry-point role relative to the sibling data tools, which is the key routing decision. It does not spell out when-not-to-use or name a specific alternative, but the surrounding context makes the intent unambiguous.
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.