Skip to main content
Glama

pje_buscar_processo

Search for specific judicial processes by ID in Brazil's Electronic Judicial Process (PJE) system using digital certificates for secure access.

Instructions

Busca um processo específico por ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID do processo

Implementation Reference

  • Input schema definition for the 'pje_buscar_processo' tool, specifying the required 'id' parameter.
      name: "pje_buscar_processo",
      description: "Busca um processo específico por ID",
      inputSchema: {
        type: "object",
        properties: {
          id: { type: "string", description: "ID do processo" },
        },
        required: ["id"],
      },
    },
  • src/index.ts:334-336 (registration)
    Registration of the tool handler in the CallToolRequestSchema switch statement.
    case "pje_buscar_processo":
      if (!this.pjeClient) throw new Error("PJE não configurado");
      return await this.buscarProcesso(request.params.arguments);
  • Main handler function for the tool that extracts the process ID, calls PJEClient.buscarProcesso, and formats the response.
    private async buscarProcesso(args: any) {
      const { id } = args;
      const result = await this.pjeClient!.buscarProcesso(id);
    
      return {
        content: [
          {
            type: "text",
            text: `📄 **Detalhes do processo:**\n\n${JSON.stringify(result, null, 2)}`,
          },
        ],
      };
    }
  • PJEClient helper method that performs the actual HTTP GET request to the PJE API to fetch the process details by ID.
    async buscarProcesso(id: string): Promise<PJEResponse> {
      const response = await this.axiosInstance.get(`/api/v1/processos/${id}`);
      return response.data;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool searches for a specific process by ID but doesn't describe what happens if the ID isn't found, whether authentication is required, rate limits, or what the return format looks like. For a lookup tool with zero annotation coverage, this leaves significant behavioral gaps.

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, clear sentence with zero wasted words. It's appropriately sized for a simple lookup tool and front-loads the essential information (search process by ID). Every word earns its place.

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 and no output schema, the description is incomplete for a tool that likely returns process data. It doesn't explain what information is returned, error conditions, or system-specific behaviors (PJE context). For a lookup operation, users need to know what to expect in response, which is missing here.

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?

The description adds that the search is 'por ID' (by ID), which aligns with the single 'id' parameter in the schema. Since schema description coverage is 100% (the parameter already has a description 'ID do processo'), the description provides minimal additional semantic value beyond what's in the structured schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 'Busca um processo específico por ID' clearly states the action (busca/search) and resource (processo/process) with specificity about the ID parameter. It distinguishes itself from sibling tools like 'pje_listar_processos' by focusing on individual lookup rather than listing. However, it doesn't explicitly mention the system (PJE) which could provide additional context.

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?

The description implies usage when you need to find a specific process by its ID, but doesn't provide explicit guidance on when to use this versus alternatives like 'pje_listar_processos' for browsing or other search methods. No exclusions or prerequisites are mentioned, leaving usage context somewhat implicit.

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