Retrieve the official URLs for PJe/TJPE 1st and 2nd degree environments. Use this list to connect to the correct court systems without manual lookup.
Lista URLs oficiais configuradas para o PJe/TJPE de 1º e 2º graus.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.7.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must bear the full burden. It states the action is 'Lists', which implies a non-destructive read operation, but does not disclose potential side effects, prerequisites, or authentication needs. Since the tool is a simple listing, the description is adequate but minimal.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence, concise and front-loaded with the action and object. No unnecessary words or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given that there is an output schema and no parameters, the description covers the necessary information for an agent to understand the tool's purpose. It could have elaborated on the exact detail of 'oficiais configuradas' but is sufficient for a simple listing tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the baseline is 4. The description does not need to explain parameters, as there are none.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific verb ('Lista') and resource ('URLs oficiais configuradas para o PJe/TJPE de 1º e 2º graus'), making it distinct from sibling tools like 'listar_tribunais_suportados' which lists supported courts. It precisely identifies what the tool does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage—this tool is used to retrieve official PJe/TJPE environment URLs—but it does not explicitly state when to use it versus alternatives, nor any exclusions. No usage context is provided beyond the core action.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.