Skip to main content
Glama

pje_listar_assuntos

Lists procedural subjects within the Brazilian Electronic Judicial Process (PJE) system to help users identify and categorize legal case topics.

Instructions

Lista assuntos processuais

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • PJEServer.listarAssuntos(): Executes the tool logic by calling PJEClient.listarAssuntos() and formatting the response as MCP content.
    private async listarAssuntos() {
      const result = await this.pjeClient!.listarAssuntos();
    
      return {
        content: [
          {
            type: "text",
            text: `📑 **Assuntos processuais:**\n\n${JSON.stringify(result, null, 2)}`,
          },
        ],
      };
  • PJEClient.listarAssuntos(): Core API call to fetch assuntos from PJE endpoint /api/v1/assuntos.
    async listarAssuntos(): Promise<PJEResponse> {
      const response = await this.axiosInstance.get("/api/v1/assuntos");
      return response.data;
    }
  • src/index.ts:277-284 (registration)
    Tool registration in ListToolsRequestSchema handler, defining name, description, and empty input schema.
    {
      name: "pje_listar_assuntos",
      description: "Lista assuntos processuais",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Dispatch case in CallToolRequestSchema handler that checks configuration and calls the tool handler.
      if (!this.pjeClient) throw new Error("PJE não configurado");
      return await this.listarAssuntos();
    case "pje_status":
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Lista') but doesn't describe any behavioral traits such as pagination, rate limits, authentication requirements, or what format the list returns. This is a significant gap 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 assuntos processuais') that directly states the tool's purpose without any wasted words. 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 'assuntos processuais' are, how the list is structured, or any behavioral aspects like safety or performance. For a tool with no structured data beyond the input schema, more context is needed to guide effective use.

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 with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't add parameter details, which is unnecessary here. A baseline of 4 is appropriate as the schema handles all parameter documentation, and no compensation is needed.

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 assuntos processuais' clearly states the tool's purpose with a specific verb ('Lista') and resource ('assuntos processuais'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'pje_listar_classes' or 'pje_listar_orgaos_julgadores', which appear to be similar list operations for different resource types.

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. It doesn't mention prerequisites, context for use, or comparisons to sibling tools like 'pje_listar_processos' or 'pje_buscar_processo', 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