viridis-agent-fleet

by jdhart81

Overview Schema Source Related Servers Discussions Admin

Python

Remote

arbitration__list_cases

List arbitration cases with optional filtering by state: FILED, EVIDENCE_OPEN, or RULED.

Instructions

[arbitration — deterministic dispute rulings] List cases, optionally filtered by state (FILED|EVIDENCE_OPEN|RULED).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "arbitration__list_cases"
  }
}

Input Schema

Name	Required	Description	Default
`state`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.12Jul 28, 2026
Removedv0.1.11Jul 18, 2026
Changed6 schema fields changedv0.1.9Jul 16, 2026
- removedInput schema / properties / state / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / state / default
```
Removed value: -null
```
- removedInput schema / properties / state / title
```
Removed value: -"State"
```
- addedInput schema / properties / state / type
```
Added value: +"string"
```
- addedInput schema / required
```
Added value: +[]
```
- removedInput schema / title
```
Removed value: -"list_casesArguments"
```
Changed6 schema fields changedJul 13, 2026
- addedInput schema / properties / state / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- addedInput schema / properties / state / default
```
Added value: +null
```
- addedInput schema / properties / state / title
```
Added value: +"State"
```
- removedInput schema / properties / state / type
```
Removed value: -"string"
```
- removedInput schema / required
```
Removed value: -[]
```
- addedInput schema / title
```
Added value: +"list_casesArguments"
```
Changed6 schema fields changedJul 13, 2026
- removedInput schema / properties / state / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / state / default
```
Removed value: -null
```
- removedInput schema / properties / state / title
```
Removed value: -"State"
```
- addedInput schema / properties / state / type
```
Added value: +"string"
```
- addedInput schema / required
```
Added value: +[]
```
- removedInput schema / title
```
Removed value: -"list_casesArguments"
```
First observedJul 13, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations provided. Description indicates it lists cases and supports optional filtering, but does not disclose read-only nature, pagination, rate limits, or scope of data returned. Gains some transparency from prefix 'deterministic dispute rulings' but insufficient for full behavioral understanding.

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?

Extremely concise: one sentence with a brief prefix. All information is front-loaded and no unnecessary words.

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?

Missing output description, no mention of return format, ordering, pagination, or any additional details about the list. Given no output schema, the description should at least hint at what the response contains.

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?

Schema has 0% description coverage. Description compensates well by naming the parameter 'state' and listing allowed values (FILED|EVIDENCE_OPEN|RULED), which adds critical context missing from the schema.

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

Purpose5/5

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

The description clearly states the verb 'List' and the resource 'cases', and the prefix provides domain context. It distinguishes from siblings like arbitration__get_case (single case) and arbitration__file_case (create).

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?

Implied usage: use for listing cases with optional filtering. No explicit guidance on when or when not to use this tool compared to siblings like arbitration__get_case or arbitration__file_case. Lack of alternative recommendations.

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

Deploy Server