Skip to main content
Glama

Home buying scheme eligibility

scheme_eligibility
Read-onlyIdempotent

Use this for whether someone qualifies for a government home buying scheme: shared ownership, First Homes, Your First Home, Deposit Unlock, Lifetime ISA, the Mortgage Guarantee Scheme, Rent to Buy, Own New and the closed Help to Buy equity loan. Each scheme comes back likely eligible, possibly eligible (local rules unconfirmed) or not eligible, with the rule that decided it, its source, and the facts still needed. With no facts, it lists every scheme and whether it is open.

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

Input Schema

NameRequiredDescriptionDefault
agesNoEach buyer’s age.
homeNoA home page address from a search: its price, nation and builder offers are used.
priceNo
nationNoWhere the home is. Scotland pays LBTT and Wales LTT; England and Northern Ireland stamp duty.
depositNo
schemesNo
employedNo
key_workerNo
with_mortgageNo
owns_a_home_nowNo
first_time_buyerNo
household_incomeNo
in_greater_londonNo
lifetime_isa_first_paymentNoThe date of the first payment into a Lifetime ISA, if one is held.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the lower bar applies. The description still adds real behavioral detail beyond those: the three-valued eligibility outcome, the accompanying deciding rule, source, and remaining facts needed, plus the all-schemes behavior when no inputs are supplied. It does not describe response format or partial-fact handling, which keeps it from a 5.

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?

Three front-loaded sentences with no filler. The scheme enumeration is long but earns its place by defining scope, and the output and zero-facts behaviors follow in logical order. Minor cost is the length of the list, but it is informative rather than redundant.

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

Completeness3/5

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

For a 14-parameter tool without an output schema, the description does well on outcome semantics and the empty-input case, which an agent needs. It is weaker on input semantics: the majority of parameters are undocumented in both schema and description, leaving ambiguity about what facts drive which eligibility rules.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 29% across 14 parameters, so the description is expected to compensate. It gives no explanation of price, deposit, schemes, household_income, first_time_buyer, key_worker, or the other undocumented inputs; only the phrase 'with no facts' hints that everything is optional.

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 states a specific verb and resource ('whether someone qualifies for a government home buying scheme') and then enumerates the nine schemes covered, including the closed Help to Buy equity loan. No sibling tool competes with this scope, so an agent can identify it immediately.

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

Usage Guidelines4/5

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

It opens with an explicit 'Use this for...' directive and explains the zero-facts mode ('lists every scheme and whether it is open'), which is a concrete usage pattern. It stops short of naming when to prefer siblings such as affordability_calculator or stamp_duty_calculator, so there are no explicit exclusions or alternatives.

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