Conector Juspronto

Consultar clientes

buscar_clientes

Read-only

Busque clientes do escritório, inclusive sem processo, por texto (nome, CPF/CNPJ parcial, e-mail ou telefone). Sem texto, lista todos em páginas de até 20; continue com cursor e os mesmos filtros. Abra ficha com clienteId; processosCursor continua seus vínculos. Retorna id, nome (iniciais para menor com nascimento conhecido), clienteCienteUsoIa, 20 processos mais recentes por criação (id, numeroProcesso e titulo), totalProcessos, continuarProcessos com os argumentos da próxima página e link da ficha. Nos dois perfis, CPF/CNPJ, e-mail, endereço, telefone, WhatsApp, RG, nascimento e observação não saem. Consulte documento e contato na ficha pelo link. Não cadastra, edita, exclui, envia mensagens nem consulta pagamentos; não confirma identidade só pelo nome.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "buscar_clientes"
  }
}

Input Schema

Name	Required	Description
`texto`	No	Nome, documento parcial, e-mail ou telefone
`cursor`	No	proximoCursor da busca anterior, com os mesmos filtros
`clienteId`	No	ID do cliente para abrir a ficha; não combine com texto ou cursor
`processosCursor`	No	Cursor de continuarProcessos.argumentos; use com o mesmo clienteId

Output Schema

Name	Required	Description	Default
`aviso`	No
`itens`	No
`total`	No
`truncado`	No
`avisoConteudo`	No
`proximoCursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, but the description adds substantive behavior: contact and document fields are withheld in both profiles, only the 20 most recent processes are returned, minors' names appear as initials when birth date is known, and continuation works with the previous cursor plus identical filters. Pagination semantics and the redaction rule go well beyond the structured hints. It stops short of full transparency only on rate limits or error behavior.

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?

Front-loaded with the core action, then pagination, then the ficha path, then exclusions — a logical order with no filler. It is dense though: several clauses are chained with semicolons, and the return-value enumeration could be compressed since an output schema exists.

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?

For a read-only search tool with four optional parameters, the definition covers query modes, pagination continuation, the ficha branch, redaction rules and explicit non-capabilities. Even setting aside the output schema, an agent has everything needed to call it correctly on the first attempt.

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

Parameters3/5

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

Schema coverage is 100% and the schema already states that clienteId must not be combined with texto or cursor, so the baseline is 3. The description reinforces the constraint by tying cursor to "os mesmos filtros" and processosCursor to "o mesmo clienteId", but adds little syntax or format detail beyond the schema text.

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 a specific verb and resource ("Busque clientes do escritório"), the searchable fields (nome, CPF/CNPJ parcial, e-mail, telefone) and the scope ("inclusive sem processo"), which separates it from process-oriented siblings like buscar_processos. It also negates adjacent capabilities (no cadastro, edição, exclusão, mensagens, pagamentos), so an agent can place it precisely among the 33 siblings.

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?

Gives the when: free text search by name/document/e-mail/phone, and the fallback when texto is absent (lists all, 20 per page). It also routes the two follow-up paths explicitly — clienteId to open the ficha, processosCursor to continue vínculos — and warns not to confirm identity by name alone.

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

All Conector Juspronto tools Inspect

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

Need Help?