LION - keyless x402 data + RPC for agents

by dev.workers.lionmaster-operations.lion-x402

lion_poi_business_search

Point of interest / business search (keyless, OSM) [x402 paid: GET /api/x402/poi-business-search-json price $0.01 on Base]

Input Schema

TableJSON Schema

Name	Required	Description	Default
`q`	Yes
`lat`	No
`lon`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 12, 2026
RemovedAug 25, 2026

Changed9 schema fields changedJul 17, 2026

removedInput schema / properties / area

Removed value: -{
-  "description": "Place name to search within, geocoded to a bounding box, e.g. \"Soho, New York\". Provide this OR bbox.",
-  "type": "string"
-}

removedInput schema / properties / bbox

Removed value: -{
-  "description": "Explicit bounding box \"south,west,north,east\" in decimal degrees. Provide this OR area.",
-  "type": "string"
-}

removedInput schema / properties / category

Removed value: -{
-  "description": "Preset category: food, restaurant, cafe, bar, retail, grocery, hotel, health, pharmacy, finance, bank, fuel, automotive, education, gym. Provide this OR tag.",
-  "type": "string"
-}

addedInput schema / properties / lat
```
Added value: +{
+  "type": "number"
+}
```

removedInput schema / properties / limit

Removed value: -{
-  "description": "Max results (default 25, max 50).",
-  "type": "number"
-}

addedInput schema / properties / lon
```
Added value: +{
+  "type": "number"
+}
```
addedInput schema / properties / q
```
Added value: +{
+  "type": "string"
+}
```

removedInput schema / properties / tag

Removed value: -{
-  "description": "Raw OSM tag filter \"key=value\" (key in amenity|shop|tourism|leisure|office|craft|healthcare), e.g. \"shop=bakery\". Provide this OR category.",
-  "type": "string"
-}

addedInput schema / required
```
Added value: +[
+  "q"
+]
```

AddedJun 3, 2026

TDQS

B3/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose useful behavior: keyless access, OSM as the data source, an x402 payment endpoint, and a $0.01 cost on Base. That payment/cost disclosure is genuinely valuable. It still omits what the search returns, latency, rate limits, and how lat/lon vs q interact.

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

Conciseness4/5

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

A single front-loaded line that leads with the purpose and appends access/pricing metadata in brackets. Minimal waste, though the x402 bracket is dense and could have been split for readability.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-param search tool with no annotations and no output schema, the description covers source and cost but leaves parameter semantics and return shape unspecified. It is minimally adequate for invocation but not for confident selection or correct argument usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for 3 parameters, and the description explains none of them. Only 'q' (query) and lat/lon (coordinates) can be guessed from the POI framing; there is no statement of format, coordinate convention, or whether q is required alongside coordinates.

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

Purpose4/5

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

States a specific verb+resource (POI/business search) and adds distinguishing context via '(keyless, OSM)', which differentiates it from company/dossier siblings. However, it never names an alternative tool or explicitly contrasts with lion_web_search or lion_scrape, so differentiation is implied rather than stated.

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?

There is no when-to-use or when-not-to-use guidance. 'keyless' hints at an access mode but not a selection condition, and no alternative sibling is named despite 30+ siblings in the set. The agent must infer usage entirely.

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

All LION - keyless x402 data + RPC for agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?