Skip to main content
Glama
Sign In
protheus-mcp-server (piloto)

protheus-mcp-server (piloto)

by Endrews-DFL
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Saldo em aberto do cliente (WSRSALDOCLIENTE)

protheus_saldo_cliente

Retrieve a client's open accounts receivable balance by providing the client code.

Instructions

Retorna o saldo em aberto (títulos a receber, SE1) de um cliente. Informe o código do cliente. Empresa/filial são fixadas em 03/01 pelo web service.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cliente": "<cliente>"
    },
    "name": "protheus_saldo_cliente"
  }
}

Input Schema

NameRequiredDescriptionDefault
clienteYesCódigo do cliente (E1_CLIENTE) — obrigatório.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It reveals that company/branch are fixed to '03/01', which is helpful. But it does not mention if the operation is read-only, whether authentication is needed, or what database table is accessed (SE1).

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

Conciseness5/5

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

Two concise sentences, front-loaded with the purpose. Every word is relevant.

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

Completeness4/5

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

For a simple query with one parameter and no output schema, the description is adequate. It provides enough context for an agent to use the tool correctly, though it omits the output format.

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?

Schema coverage is 100% (one parameter). The description adds meaning by stating the parameter is mandatory, specifying the SAP field name (E1_CLIENTE), and noting it's the client code.

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

Purpose4/5

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

The description clearly states the tool returns the open balance (receivables) of a client, using the verb 'Retorna' and specifying the resource. It differentiates from sibling tools like 'protheus_limite_credito_cliente' but could be more explicit.

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

Usage Guidelines3/5

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

It tells the user to provide the client code and notes that company/branch are fixed. However, it does not explicitly state when to use this tool versus alternatives, or any prerequisites.

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

Deploy Server

Other Tools