Locus Protocol (Gryd.world)

Most tools target distinct resources and actions, and descriptions include explicit endpoints. Minor overlap exists between agents_nearby (nearby agents by lat/lng/radius) and list_agents (all agents, optionally geo-filtered), which could cause misselection for nearby-agent queries.

All names use snake_case, but the word-order convention is mixed: many are verb_noun (list_agents, get_pin, build_mint_payload), while others are noun-first (market_agents, market_ordinals, agents_nearby, global_activity). The market_* pair is internally consistent, but the set lacks a single predictable pattern.

13 tools is well-scoped for the protocol: read endpoints for pins, agents, cities, inscriptions, activity, and markets; build payloads for mint and place; a transaction registrar; and documentation links. Each tool appears to earn its place without excessive redundancy.

The surface covers the core read/build/register lifecycle for the protocol, including payload construction and transaction registration. Minor gaps exist, such as no dedicated get-by-id for agents or cities and no list_inscriptions operation, but these are not severe given the list endpoints likely supply enough detail.