Skip to main content
Glama

Submit a case

evictions_submit_case
Destructive

Use this when the person has said yes to submitting a draft that passes every check. Input: the case id and confirmedByPerson. A live case is submitted when its platform fee is paid: until then this answers payment_required with the charge (chargeId) and it stays a draft. Once the person pays (evictions_get_payment_link), it moves to submitted and a licensed attorney in the property’s state is engaged for it; nothing is served or filed until that attorney has reviewed it. An agent_filed case is refused until the person finishes it in the app (facts, authorization, card). A test case is fictional, its review simulated. With a live key this acts on a real case. Confirm with the person first, then pass confirmedByPerson: true. The case’s attestations must be the person’s own statements; never fill them in yourself. Do not use this to check a draft (use evictions_validate_case). Returns the case and its check results. 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>",
      "confirmedByPerson": "<confirmedByPerson>"
    },
    "name": "evictions_submit_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe case id (case_...), as returned by evictions_create_case or evictions_list_cases.
confirmedByPersonYesSet to true only after the person has said yes to this exact action on this case, in this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds substantial unrecoverable-outcome detail: an unpaid case answers 'payment_required' with a chargeId and remains a draft, a paid one moves to submitted and engages a state-licensed attorney, and nothing is served or filed until attorney review. It also discloses the live-key scope and the refusal path for agent_filed cases. The only minor gap is that it doesn't say whether a refused or payment-pending call is retryable without side effects, though idempotentHint=false in the annotations covers part of that.

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?

The trigger condition is front-loaded in the first sentence, and each subsequent sentence carries distinct decision-relevant information (payment gate, attorney engagement, agent_filed refusal, test mode, attestation integrity). It is dense and somewhat run-on for a single paragraph, but there is essentially no filler to cut.

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?

No output schema exists, yet the description still tells the agent what comes back ('Returns the case and its check results') and describes the alternate 'payment_required' response shape with chargeId. Combined with the state-transition rules, the destructive-write annotations, and both parameters fully documented, an agent has everything needed to call this correctly or decide not to.

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 the baseline is 3. The description reinforces the gating on confirmedByPerson ('Confirm with the person first, then pass confirmedByPerson: true') and frames the id as the draft's case id, but most of this restates what the schema's own property descriptions already say, adding little syntactic or semantic detail beyond that.

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?

States a specific action (submit a draft case) gated on an explicit precondition ('the person has said yes to submitting a draft that passes every check'), and explicitly names the sibling it is not ('Do not use this to check a draft (use evictions_validate_case)'). An agent can distinguish this from validate_case and get_payment_link 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?

Gives when-to-use ('person has said yes'), when-not ('Do not use this to check a draft'), and the alternative by name. It also covers the preconditions that block submission — unpaid platform fee, unfinished agent_filed case, and test-vs-live keys — so the agent knows which state the case must be in before calling.

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.