Skip to main content
Glama

pje_listar_classes

Lists procedural classes from the Brazilian Electronic Judicial Process (PJE) system to help users identify and navigate legal case types.

Instructions

Lista classes processuais

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'pje_listar_classes' tool in PJEServer class. It calls PJEClient.listarClasses() and formats the result as a text response.
    private async listarClasses() {
      const result = await this.pjeClient!.listarClasses();
    
      return {
        content: [
          {
            type: "text",
            text: `📚 **Classes processuais:**\n\n${JSON.stringify(result, null, 2)}`,
          },
        ],
      };
  • src/index.ts:340-342 (registration)
    Registration and dispatch for the 'pje_listar_classes' tool in the CallToolRequestSchema switch statement.
    case "pje_listar_classes":
      if (!this.pjeClient) throw new Error("PJE não configurado");
      return await this.listarClasses();
  • Tool schema definition including name, description, and input schema (empty properties) in the ListToolsRequestSchema response.
    {
      name: "pje_listar_classes",
      description: "Lista classes processuais",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Helper method in PJEClient class that performs the actual API call to fetch classes from '/api/v1/classes'.
    async listarClasses(): Promise<PJEResponse> {
      const response = await this.axiosInstance.get("/api/v1/classes");
      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 of behavioral disclosure. It only states the basic action ('Lista classes processuais') without any information on permissions, rate limits, pagination, or what the output looks like. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 classes processuais') that directly states the tool's purpose with zero waste. It is appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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 the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'classes processuais' are, how the listing is formatted, or any behavioral traits like safety or performance. For a tool in a legal context with sibling tools, more context is needed to ensure proper usage.

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 input schema has 0 parameters with 100% coverage, meaning there are no parameters to document. The description doesn't need to add parameter semantics, so it meets the baseline expectation for a parameterless tool, though it doesn't provide extra context about implicit inputs or defaults.

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 'Lista classes processuais' clearly states the action (list) and resource (procedural classes), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'pje_listar_assuntos' or 'pje_listar_orgaos_julgadores' that also list different types of entities, so it doesn't fully distinguish its scope from similar operations.

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?

The description provides no guidance on when to use this tool versus alternatives. There are multiple sibling listing tools (e.g., 'pje_listar_assuntos', 'pje_listar_processos'), but the description doesn't explain when to choose this one over others or any prerequisites for its use, leaving the agent without contextual direction.

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