Skip to main content
Glama

Realtors Dashboard

Published real estate datasets

list_published_datasets
Read-onlyIdempotent

Discover published nationwide market data, Florida recorded sales, and the NYC property, sale and comparable data. Includes coverage, provenance and available operations.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds value beyond that by disclosing the content of the response: coverage, provenance, and available operations, which tells the agent this is a metadata catalog rather than raw records. It does not describe the shape or size of the listing, which keeps it out of 5 territory.

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?

Two short sentences, front-loaded with the discovery action and the data domains, followed by what metadata comes back. Every clause carries information; the only mild waste is the promotional tone of 'Discover'.

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 no parameters and no output schema, the description carries the burden of explaining what comes back, and it does so at a useful level (datasets plus coverage, provenance, operations). For a simple zero-argument listing tool this is close to sufficient, with only the concrete result format left unstated.

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 takes zero parameters, so the baseline is 4 and there is no parameter semantics for the description to explain. The empty schema with additionalProperties=false is consistent with the description's framing as a fixed, no-argument discovery call.

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 gives a specific verb ('Discover') and enumerates the resource families it covers: nationwide market data, Florida recorded sales, and NYC property/sale/comparable data. It also states the metadata returned (coverage, provenance, available operations), so an agent can tell this is a catalog/listing tool rather than a data-query tool like its siblings. It stops short of explicitly contrasting itself with those siblings, so it is not a 5.

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 word 'Discover' plus 'available operations' implies this is an orientation/entry-point call before drilling into the more specific sibling tools, but that is left to inference. There is no explicit 'use this when...' statement, no exclusion of alternatives, and no guidance on whether it must be called first or can be skipped.

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.