Skip to main content
Glama

Describe the Boardwalk dataset

describe_data
Read-onlyIdempotent

What this dataset can and cannot answer. Returns groupable fields (Building type, city, county, Construction Type), metrics, denominators, coverage, and a notAnswerable list (denial rates, time-to-entitlement, project value, affordability). Does not use credits. Returns no project records. Covers both datasets: planned projects (datasets.projects) and building permits (datasets.permits, with its own fields, metrics, coverage, and notAnswerable list). Searches return private leads by default. leadTypes (for example ["private","public"]) widens that set. Standard and full records carry leadType and stage; compact omits them.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The description adds useful behavior beyond the annotations by stating that it does not use credits, returns no project records, and covers both the projects and permits datasets. However, much of the remaining text about searches returning private leads by default, leadTypes widening the set, and record variants carrying leadType and stage is not clearly connected to this zero-parameter describe tool and adds ambiguity rather than invocation-relevant transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description front-loads the core purpose and return categories, but it becomes less structured as it moves into search defaults, leadTypes, and record variants that are not obviously relevant to calling describe_data. Those sentences dilute focus even though the overall length is not excessive.

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 output schema and no parameters, the description carries most of the burden for explaining what comes back, and it does list the main returned categories and coverage scope across both datasets. It is complete enough for an agent to understand the tool’s value, though clearer output structure or explicit usage sequencing would improve it.

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?

This tool has zero parameters, so there is no parameter semantics to explain. The baseline for a no-parameter tool applies, and the description appropriately focuses on returned dataset metadata rather than inputs.

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 states that this tool describes what the dataset can and cannot answer, and it enumerates returned components such as groupable fields, metrics, denominators, coverage, and notAnswerable items. It distinguishes this as metadata rather than project-record retrieval by saying it returns no project records, though it does not explicitly contrast itself with sibling tools.

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 'what this dataset can and cannot answer' implies using this tool to scope whether a question is answerable, and the notAnswerable list supports that. However, there is no explicit instruction on when to call it versus alternatives, no prerequisite guidance, and no direct routing to other tools for searches or records.

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