Skip to main content
Glama

UPí — upCampo

by br.com.upcampo
OverviewDiscussionsAdmin

Listar fazendas

listar_fazendas
Read-only

Diz com qual usuário upCampo a conexão está autenticada e lista as fazendas (filiais) que ele pode consultar, com a empresa, os assuntos liberados em cada uma e qual é a fazenda corrente. Use quando o usuário perguntar quais fazendas tem, ou quando citar uma fazenda por um nome que você precisa conferir. Não é necessária antes de uma consulta comum: sem fazenda informada, as tools já usam a corrente.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
avisoNo
totalYes
usuarioYesNome do usuário upCampo desta conexão.
fazendasYes
conexao_pode_lancarYesSe ESTA conexão foi autorizada a lançar. Falso significa que as tools de lançamento vão recusar, mesmo onde a fazenda permitir.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / fazendas / items / properties / cadastros_editaveis
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedOutput schema / properties / fazendas / items / required
      Previous value: -[
-  "nome",
-  "empresa",
-  "identificador",
-  "corrente",
-  "consultas_liberadas",
-  "lancamentos_liberados"
-]New value: +[
+  "nome",
+  "empresa",
+  "identificador",
+  "corrente",
+  "consultas_liberadas",
+  "lancamentos_liberados",
+  "cadastros_editaveis"
+]
  2. Changed2 schema fields changed
    • changedOutput schema / properties / conexao_pode_lancar / description
      Previous value: -"Se ESTA conexao foi autorizada a lancar. Falso significa que as tools de lancamento vao recusar, mesmo onde a fazenda permitir."New value: +"Se ESTA conexão foi autorizada a lançar. Falso significa que as tools de lançamento vão recusar, mesmo onde a fazenda permitir."
    • changedOutput schema / properties / usuario / description
      Previous value: -"Nome do usuario upCampo desta conexao."New value: +"Nome do usuário upCampo desta conexão."
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: it reports the authenticated user, the company, released subjects per farm, and the current farm, which helps the agent interpret the result. It omits any auth preconditions or rate-limit notes, keeping it just below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with what the tool returns before the usage guidance. The final sentence about not being needed before a common query is valuable but slightly leaning, keeping it just under maximally tight. No filler or repetition.

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

Completeness5/5

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

An output schema exists so return values need not be spelled out, yet the description still summarizes the returned content (user, farms, company, subjects, current farm), and the usage guidance is complete. Nothing an agent needs in order to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a no-argument, context-resolving call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States specific verbs and resources: it reports the authenticated upCampo user and lists the farms (branches) available, along with company, released subjects, and the current farm. This is clearly distinguishable from sibling list tools like listar_safras and the cadastrar/consultar family.

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

Usage Guidelines5/5

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

Explicitly gives when to use (user asks which farms exist, or cites a farm name to verify) and when not to (not required before a common query, since tools default to the current farm). This directly routes the agent and prevents a needless call.

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

All UPí — upCampo toolsInspect
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