Skip to main content
Glama

Check a draft case

evictions_validate_case
Read-onlyIdempotent

Use this when a draft looks complete, before asking the person to confirm its submission. Input: the case id. Runs the submission checks on a draft and returns each check’s result, with the reason when it does not pass, and whether all passed; missing names what is still needed (with, for an item that was looked for in the person’s documents and not found, a sentence in missingReasons saying why and what to do), and filledFromDocuments names the answers that were read from the person’s uploaded documents, to check with the person. Changes nothing. Do not use this to submit (use evictions_submit_case). Next: evictions_update_case to fill a gap, or the person’s yes and then evictions_submit_case. Needs the person’s account: sign-in or an API key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe case id (case_...), as returned by evictions_create_case or evictions_list_cases.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations it adds the auth requirement ('Needs the person's account: sign-in or an API key') and confirms non-mutation. Crucially, with no output schema present it describes the return payload — per-check results, failure reasons, an overall pass flag, plus `missing`, `missingReasons`, and `filledFromDocuments` — including the human-in-the-loop meaning of `filledFromDocuments` (verify with the person), which annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the trigger condition, then the input, then the returns, then the exclusions and next steps — a logical order with no filler sentences. The middle sentence is long and nests a parenthetical inside a parenthetical, which costs some readability but does not waste content.

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 one-parameter validation tool with no output schema, the definition supplies everything an agent needs: when to call, what it returns (including how to interpret `missing`/`missingReasons`), that it mutates nothing, auth prerequisites, and what to do next on pass or fail.

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 coverage is 100% and the single `id` parameter is already documented as a case_... id returned by create/list. The description only restates 'Input: the case `id`' and adds no format or sourcing detail beyond the schema, so the baseline of 3 applies.

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 names a specific verb and resource — running the submission checks on a draft case — and explicitly frames it as a pre-submission validation step, which distinguishes it from evictions_submit_case and evictions_get_case. An agent knows exactly what the tool does without opening the 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 an explicit trigger ('when a draft looks complete, before asking the person to confirm its submission'), an explicit exclusion ('Do not use this to submit (use evictions_submit_case)'), and a follow-up decision path (evictions_update_case to fill a gap, then evictions_submit_case). Alternatives and their selection conditions are spelled out rather than inferred.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.