Skip to main content
Glama

Houski Property Data

field_list

List the name of every public property data field, one per line. Does not bill per call. Pass filter to list only the names that contain a piece of text, for example score_, demographic_, assessment, permit or expand_listing. Follow with field_detail for each field's type, accepted filter values, aggregation support, expand set and price per value returned.

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

Input Schema

NameRequiredDescriptionDefault
filterNoOptional text to match inside field names, for example "score_", "demographic_", "assessment", "permit" or "expand_listing". Leave it out to list every field.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose two non-obvious traits: 'Does not bill per call' (cost behavior, important against a metered API) and the line-oriented output format. It omits auth requirements, rate limits, and result-size limits, which keeps it from a 5 for an unannotated 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?

Four short sentences, front-loaded with the core action and output format before the filter guidance and the follow-up step. The filter examples duplicate the schema text verbatim, which is the only wasted space.

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?

A one-parameter, read-only enumeration tool with no output schema needs exactly this: what is listed, how it is formatted, what it costs, and which tool to call next. Nothing an agent requires to invoke it correctly is missing.

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 coverage is 100%, so the single filter parameter and its example values are already documented in the schema. The description restates the same examples ('score_', 'demographic_', 'assessment'...) and adds the substring-match semantics only implicitly via 'contain a piece of text'. Baseline 3 applies when the schema does the heavy lifting.

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 ('List the name of every public property data field'), plus the output shape ('one per line'). It also distinguishes itself from the sibling field_detail by framing itself as the enumeration step that precedes per-field detail.

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?

Gives explicit conditional guidance: pass filter to narrow to matching names, omit it to list everything, and follow with field_detail for richer metadata. It does not state any when-not-to-use condition, but the routing to the sibling is clear enough that an agent knows the intended workflow.

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