CryptoPulse Data API

halal_city

[$0.01 USDC per call via x402] Halal places in a named city (geocoded), e.g. city=Houston, TX. Up to 50 results sorted by distance from the city centre, optional cuisine filter. OpenStreetMap data (ODbL).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "city": "<city>"
    },
    "name": "halal_city"
  }
}

Input Schema

Name	Required	Description
`city`	Yes	City name, optionally with region/country, e.g. 'Houston, TX' or 'Birmingham, UK'
`limit`	No	Max results, 1-50 (default 30)
`cuisine`	No	Filter by cuisine substring
`radius_km`	No	Radius from city centre in km, 1-30 (default 15)

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does a good job: it discloses per-call cost, x402 payment, OSM/ODbL data provenance, a 50-result cap, and distance sorting from the city centre. It does not explain payment flow details, rate limits, or error behavior, so it stops short of full transparency.

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 compact and front-loaded with the cost and core purpose. Every sentence contributes relevant information: cost/payment, city scope, result limit and ordering, cuisine filter, and data licensing.

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

Completeness4/5

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

For a four-parameter search tool with full schema coverage and no output schema, the description gives enough context to call it correctly: city input, result cap, sorting, cuisine filtering, data source, and cost. It omits radius_km-specific context and the shape of returned place records, but those gaps are minor.

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 coverage is 100%, so all parameters are already documented in the input schema. The description adds useful meaning around city geocoding and result sorting, but it does not add syntax or semantics beyond the schema for limit, cuisine, or radius_km.

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?

The description clearly identifies the resource and scope: halal places in a named, geocoded city, with example input. It implicitly distinguishes itself from halal_near by requiring a city rather than coordinates, but it does not explicitly name or contrast with sibling tools.

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

Usage Guidelines3/5

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

Usage is implied by the city-based query scope and the example 'city=Houston, TX'. However, there is no explicit guidance on when to use this tool versus halal_near or halal_place, and no exclusions or prerequisites are stated.

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

All CryptoPulse Data API 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?