Machine-payable MCP tools using x402. Agents discover priced capabilities and pay per call without API keys.
Scored across 3 tools
Each tool is clearly distinct: find_construction_leads, health, and square have entirely separate purposes with no functional overlap. An agent cannot confuse them.
find_construction_leads follows a clear verb_noun pattern, but health and square are bare nouns/verbs, breaking the convention. Still readable, but the set mixes styles.
At only 3 tools the surface is thin, and two of them (health, square) are unrelated utility/infra stubs rather than domain tools. The count feels incidental rather than scoped to a coherent purpose.
For a construction-lead domain there is only a single find operation with no detail retrieval, filtering, or follow-up primitives, and square/health contribute nothing to the stated purpose. The surface is largely incomplete for any workflow.
Find newly issued Horry County construction permits that may create sales opportunities for networking, low-voltage, security, AV, POS, electrical, or related contractors. Returns ranked leads with transparent trigger signals and project details.
Inputs: trade (required), city, days_back, min_score, +2 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.