code402

Rental Risk Summary

rental_verdict

Read-onlyIdempotent

Combine deposit identifier checks with supplied country, viewing and listing indicators. Does not verify landlord identity, property ownership or safety of payment.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "deposit_iban": "GB82WEST12345698765432",
      "landlord_lei": "529900T8BM49AURSDO55",
      "property_country": "DE",
      "deposit_before_viewing": true
    },
    "name": "rental_verdict"
  }
}

Input Schema

Name	Required	Description
`deposit_iban`	Yes	Deposit IBAN.
`landlord_lei`	No	Landlord LEI (optional).
`property_country`	No	Property country, ISO alpha-2.
`urgency_pressure`	No	Pressure to secure the property today.
`landlord_company_no`	No	Landlord UK company number (optional).
`no_in_person_viewing`	No	No in-person or video viewing before payment.
`payment_irreversible`	No	Payment demanded via crypto/gift-card/wire-only.
`deposit_before_viewing`	No	True if a deposit is demanded before any viewing.
`price_below_market_pct`	No	How far below local market the rent is asked, in percent.
`contact_moves_offplatform`	No	Contact pushed off the listing platform.

Output Schema

Name	Required	Description	Default
`band`	No
`tool`	No
`flags`	No
`scope`	No
`summary`	No
`verdict`	Yes
`components`	No
`risk_score`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations are standard operational hints (readOnlyHint, idempotentHint). The description adds specific, high-level functional behavioral limits by clarifying that it focuses on risk indicators rather than comprehensive legal or safety verification of parties or assets.

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?

It uses two highly dense, perfectly phrased sentences. Every word contributes to defining the scope and limits of the tool, leaving no fluff.

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?

Given the complexity (10 parameters) and the wealth of sibling tools, this description successfully defines the tool's niche in the risk verification flow, clearly stating its input requirements and boundaries.

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 coverage is 100%, establishing a baseline of 3. The description adds conceptual grouping by lumping IBAN checks, country data, viewing indicators, and listing factors into one cohesive workflow, which is a helpful semantic organization for the agent.

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

Purpose4/5

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

The description clearly states the tool's function is to 'Combine deposit identifier checks with supplied country, viewing and listing indicators' to provide a risk summary. It distinguishes itself from pure validator tools (like iban_check) by focusing on the holistic assessment.

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 provides explicit exclusion criteria, stating what the tool does not verify ('Does not verify landlord identity, property ownership or safety of payment'). This is crucial for preventing the agent from relying on this tool as a final vetting step.

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

All code402 tools Inspect

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.