The whole decision tree
checker_treeEvery question, option and verdict of the Landlord registration and licensing checker guide, for reasoning end to end.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
site
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.7/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It does communicate that the tool exposes every question, option, and verdict, implying a read-oriented, complete-data response. However, it does not state side effects, output structure, potential size, or any caveats about how the tree is delivered.
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?
The description is a single concise sentence that front-loads the full scope ('Every question, option and verdict') and then states the purpose. There is no filler or redundancy; every phrase contributes to agent understanding.
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?
For a parameterless tool with no output schema, the description adequately tells an agent that the full decision tree is available for end-to-end reasoning. It is slightly incomplete in that it does not describe how the tree is represented or how this tool relates to checker_start and checker_answer, but these gaps are minor given the absence of required inputs.
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?
The tool has zero parameters, so there is nothing for the description to document. The schema coverage is vacuously 100%, and the description correctly avoids inventing parameter details. This matches the baseline expected for a parameterless tool.
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 identifies the resource as the complete decision tree for the Landlord registration and licensing checker and states its purpose: end-to-end reasoning. It is distinguishable from sibling tools like checker_answer or checker_start by the explicit scope of the entire tree. However, it lacks an action verb such as 'returns' or 'retrieves', so it reads as a content statement rather than a clear tool operation.
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 phrase 'for reasoning end to end' implies this tool is meant for situations where the full decision tree is needed, and sibling names suggest interactive step-by-step alternatives. There is no explicit guidance on when to prefer this tool over checker_start or checker_answer, and no exclusion or alternative conditions are stated.
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.
TDQS
A3.9/5.0
Disambiguation4/5
The tool purposes are mostly distinct: checker_start begins the guide, checker_answer advances it, and checker_tree provides the full decision tree for reasoning. There is minor overlap between checker_answer and checker_tree, but the descriptions clarify their intended uses enough to avoid serious misselection.
Naming Consistency3/5
Naming is readable but not fully consistent: checker tools use a checker_ prefix, while enquiry tools mostly use an enquiry_ prefix, and submit_enquiry reverses the pattern to verb_noun. The mixed orientation is understandable but lacks a single predictable convention.
Tool Count5/5
With 6 tools covering two well-defined workflows—the landlord checker decision guide and the enquiry submission process—the count feels appropriately scoped. Each tool earns its place without redundancy or bloat.
Completeness5/5
The checker workflow is fully covered by start, answer, and tree, allowing both interactive and end-to-end reasoning. The enquiry workflow is also complete with describe, fields, and submit covering explanation, data collection, validation, consent, and submission.