Skip to main content
Glama

Evictions API

by io.github.evictionsapi
OverviewDiscussionsAdmin

List cases

evictions_list_cases
Read-onlyIdempotent

Use this when you need the person’s cases, or the id of a case you do not have. Input: optional limit and cursor, and landlordId for only one landlord’s cases (none for the cases with no landlord). Returns the cases of the key’s organization and mode (test or live), newest first, a page at a time, each with its state and nextAction, and nextCursor for the next page (null on the last). Do not use this when you already have the case id (use evictions_get_case). Needs the person’s account: sign-in or an API key.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return, at most 100. The default is 20.
cursorNo`nextCursor` from the page before, for the next page. Leave it out for the first page.
landlordIdNoOnly the cases of this landlord (lnd_..., from evictions_list_landlords), or `none` for the cases with no landlord.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / landlordId
      Added value: +{
+  "description": "Only the cases of this landlord (lnd_..., from evictions_list_landlords), or `none` for the cases with no landlord.",
+  "pattern": "^[A-Za-z0-9_-]{1,100}$",
+  "type": "string"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With annotations already declaring readOnly, idempotent, non-destructive behavior, the description adds substantial context beyond them: results are scoped to the key's organization and mode (test or live), ordered newest first, returned a page at a time, and include fields state, nextAction, and nextCursor (null on the last page). It also discloses the authentication requirement, which annotations do not cover.

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 front-loaded with the primary use case and then proceeds through inputs, returns, exclusions, and prerequisites in a compact paragraph. Every sentence contributes necessary information (purpose, inputs, outputs, alternative, auth), with no repetition or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paginated list tool with no output schema, the description fully explains return shape (state, nextAction, nextCursor), pagination semantics (nextCursor null on last page), ordering (newest first), scoping (organization and mode), and auth needs. Nothing an agent needs in order to call it correctly is missing.

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?

Schema description coverage is 100%, so all three parameters are already fully documented in the schema. The description restates that limit and cursor are optional and that landlordId limits results to one landlord or 'none', adding marginal value over the schema. Baseline 3 is appropriate when the schema carries the semantic load.

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 uses a specific verb ('list') and resource ('cases'), states the scope (the person's cases, the key's organization and mode), and explicitly distinguishes itself from evictions_get_case. An agent can identify the tool's function and its primary sibling alternative without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use guidance ('when you need the person’s cases, or the id of a case you do not have') and when-not guidance ('Do not use this when you already have the case id (use evictions_get_case)'). It also names the required authentication context (sign-in or API key), leaving no ambiguity about usage conditions.

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

All Evictions API toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources