UPí — upCampo

Almost every tool maps to a distinct resource+action and the descriptions are unusually explicit about boundaries (e.g. lancar_ordem_servico vs lancar_ordem_manutencao, the three romaneio tools, the purchasing chain). A few pairs invite hesitation: the mega-tool consultar_cadastros overlaps with the specialized consultar_estoque/consultar_frota/consultar_compras queries, and cadastrar_plano_manutencao vs cadastrar_plano_equipamento (create vs apply) require reading the text to separate.

A rock-solid Portuguese verb_noun convention runs throughout: cadastrar_*, consultar_*, lancar_*, gerenciar_*, aprovar_*, buscar_*, ler_*, listar_*, gerar_*, trocar_*. The same action prefix always means the same kind of operation (cadastrar = create/update cadastro, lancar = write a transaction), so naming itself rarely causes errors.

70 tools is a very heavy surface for an agent; even a genuinely broad farm ERP rarely justifies this many discrete tools. The author did consolidate queries behind a visao parameter inside consultar_* tools, which mitigates some of it, but the ~31 cadastrar_* plus ~16 lancar_* tools still make the set hard to navigate and push well past the 25+ 'too many' threshold.

Coverage is genuinely deep: CRUD-with-deactivate across every cadastral entity, a full purchasing chain (requisicao -> cotacao -> coleta -> pedido -> aprovacao), finance (titulos, baixas, transferencias, extrato), fleet/maintenance, agronomic monitoring and post-harvest. A handful of operations are deliberately pushed to the portal (passwords, PIX keys, NF-e emission, DRE accounts, safra-to-safra transfer), which agents must route around.