Skip to main content
Glama

pje_listar_orgaos_julgadores

Retrieve a list of judicial bodies from the Brazilian Electronic Judicial Process system to identify available courts and tribunals for legal proceedings.

Instructions

Lista órgãos julgadores

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler function in PJEServer class that executes the tool logic by calling PJEClient.listarOrgaosJulgadores() and formatting the response as text content.
    private async listarOrgaosJulgadores() {
      const result = await this.pjeClient!.listarOrgaosJulgadores();
    
      return {
        content: [
          {
            type: "text",
            text: `🏛️ **Órgãos julgadores:**\n\n${JSON.stringify(result, null, 2)}`,
          },
        ],
      };
    }
  • src/index.ts:337-339 (registration)
    Switch case in CallToolRequestSchema handler that routes calls to the tool's handler function.
    case "pje_listar_orgaos_julgadores":
      if (!this.pjeClient) throw new Error("PJE não configurado");
      return await this.listarOrgaosJulgadores();
  • Tool registration in ListToolsRequestSchema response, including name, description, and empty input schema (no parameters required).
      name: "pje_listar_orgaos_julgadores",
      description: "Lista órgãos julgadores",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • PJEClient helper method that performs the actual API GET request to /api/v1/orgaos-julgadores and returns the response data.
    async listarOrgaosJulgadores(): Promise<PJEResponse> {
      const response = await this.axiosInstance.get("/api/v1/orgaos-julgadores");
      return response.data;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the action ('listar') without disclosing behavioral traits like whether it's read-only, paginated, rate-limited, or requires authentication. This is inadequate for a tool with zero annotation coverage.

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?

The description is a single, efficient phrase ('Lista órgãos julgadores') that directly states the purpose without any wasted words. It's appropriately sized and front-loaded.

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

Completeness2/5

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

Given no annotations, no output schema, and a simple list operation, the description is incomplete. It lacks details on behavior, output format, or error handling, which are essential for an agent to use this tool effectively in context with siblings.

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 has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter semantics, but with no parameters, a baseline of 4 is appropriate as there's nothing to compensate for.

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

Purpose3/5

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

The description 'Lista órgãos julgadores' (Lists judging bodies) clearly states the action (list) and resource (judging bodies), but it's vague about scope or format. It doesn't distinguish from sibling tools like 'pje_listar_processos' or 'pje_listar_classes', which also list different resources.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention context, prerequisites, or exclusions, leaving the agent to infer usage based on tool names alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chapirousIA/pje-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server