Skip to main content
Glama

RemedyBridge free tools for tenants

Evidence checklist builder

build_evidence_checklist
Read-onlyIdempotent

Lists the evidence worth gathering about disrepair in a rented home, for the problems and the landlord given: what everyone should keep (dated photos, copies of every report, reference numbers, appointments and complaint letters), then what each problem needs and what each kind of landlord’s case needs. Problems: "damp" (damp or mould), "leak" (leaks or water ingress), "heating" (heating or boiler), "electrics" (unsafe electrics), "windows" (windows or doors), "pests" (pests or vermin), "structural" (structural or plaster). It asks for no personal details.

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": "build_evidence_checklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
landlordNo"council", "association" (a housing association) or "private".
problemsNoThe problems in the home, any of "damp", "leak", "heating", "electrics", "windows", "pests", "structural".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds useful context beyond that: the answer is a static prepared checklist, it covers both universal and conditional items, and explicitly 'asks for no personal details', which is a meaningful privacy disclosure for a housing-advice tool.

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 core action and the output structure before the enum glosses, and every sentence carries information. The single dense paragraph with an inline label list is slightly hard to scan, which keeps it below a 5.

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

Completeness4/5

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

With only two optional enum parameters and no output schema, the description does the necessary work of explaining what the checklist contains and that it is personalized by landlord and problems. It stops short of describing format or length of the result, but nothing critical to invoking it correctly is missing.

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%, so the baseline is 3, but the description goes further by glossing the enum values ('damp' = damp or mould, 'leak' = leaks or water ingress, 'structural' = structural or plaster) and by explaining that 'landlord' selects which landlord-specific case items are returned. That mapping between input value and output branch is real added meaning.

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 verb and resource ('Lists the evidence worth gathering about disrepair in a rented home') and spells out the output shape: common items, then per-problem items, then per-landlord items. That is clearly distinguishable from siblings that compute deadlines (calculate_landlord_complaint_deadlines, check_awaabs_law_deadlines) or supply letters (get_repair_letter_template).

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?

The description implies when this applies – you have a landlord type and a set of problems and want an evidence list – but never states when to prefer it over siblings like search_housing_repair_help or get_repair_letter_template, and gives no exclusions or prerequisites. Usage is inferable rather than guided.

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.

Resources