Skip to main content
Glama

Houski Property Data

field_detail

Describe fields by name: type, accepted filter values, its source column if it has one, filtered, aggregated or predicted, which expand set it belongs to, its price per value returned, and its full description. Does not bill per call. Coverage differs by country, and the server instructions say how to check it cheaply with location_endpoint.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "fields": "<fields>"
    },
    "name": "field_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsYesComma-separated list of field names to get details for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the whole behavioral burden and does add valuable context: 'does not bill per call' and per-value pricing. It stops short of stating what happens for unknown field names, whether all named fields must exist, or any auth/response-size characteristics.

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 then the return attributes, which is the right order. It is a single long run-on sentence with many comma-joined clauses, which slightly hurts scannability but wastes no words.

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 one-parameter read tool with no output schema, it covers what each result contains, the billing model, and the country-coverage caveat. Only the handling of invalid or unknown field names is left unstated.

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?

Only one parameter and schema coverage is 100%, with the schema already documenting it as a comma-separated list of field names. The description's 'by name' phrasing adds no format, limit, or edge-case meaning beyond that, so the baseline applies.

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?

Uses a specific verb and resource ('describe fields by name') and enumerates the attributes returned — type, accepted filter values, source column, expand set membership, price, full description. That enumeration makes it plainly distinguishable from field_list, though it never names the sibling explicitly.

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 real guidance for a prerequisite step: coverage varies by country and the cheap way to check is the location_endpoint referenced in server instructions. It does not say when to choose this over field_list or aggregate_endpoint, so usage is clear but not fully routed.

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