ChatGXT

The two tools target clearly separate concerns: one returns server/client capability metadata, the other searches public app listings. Descriptions explicitly delimit scope (capabilities vs. plugin search) and both note they are read-only and non-connecting, so an agent cannot reasonably confuse them.

Both names follow a verb_noun snake_case pattern with a consistent 'chatgxt' namespace segment (get_chatgxt_capabilities, search_chatgxt_plugins). The repeated namespace prefix makes names a bit verbose but the convention is predictable.

Two tools is thin even for a deliberately read-only discovery surface; there is no tool for fetching details on a single listing or paging through results. The count is defensible given the narrow stated scope but sits at the borderline of under-provisioned.

Discovery is covered (capabilities + search), but there is no get_plugin/listing-detail tool, so an agent that finds a plugin in search results has no way to inspect it further. The surface is coherent with its read-only purpose but has a notable dead end after search.