Skip to main content
Glama
cityjson-mcp

cityjson-mcp

by Yarroudh

List CityObjects

cityjson_list_objects

Lists CityObjects from a CityJSON dataset with IDs, types, attributes, and LoDs; filter by object type and paginate results to inspect model contents.

Instructions

List CityObjects with IDs, types, selected attributes and LoDs. Supports filtering by CityObject type and pagination.

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": {
      "dataset_id": "<dataset_id>"
    },
    "name": "cityjson_list_objects"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
typesNo
offsetNo
dataset_idYesFilename returned by cityjson_open, cityjson_import, or a transformation. Internal dataset handles also work for compatibility.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • changedInput schema / properties / dataset_id / description
      Previous value: -"Dataset handle returned by cityjson_import, cityjson_open, cityjson_import_text, or another transformation tool."New value: +"Filename returned by cityjson_open, cityjson_import, or a transformation. Internal dataset handles also work for compatibility."
  2. First observedv0.1.0

TDQS

B3.2/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. Calling it 'List' implies a read-only enumeration and 'pagination' signals result paging, but it omits the default page size of 100, the 5000 cap, and what 'selected attributes' actually means (which attributes, decided by whom). Read-only behavior and pagination are implied rather than stated.

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 with no filler, and the resource plus returned fields are front-loaded before the optional capabilities. No restructuring needed; only the vague phrase 'selected attributes' wastes a little space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description is the only source of return-value information, and it lists the returned field categories but not their shape or nesting. For a payload-listing tool with three undocumented parameters and no annotations, it covers the essentials but leaves meaningful gaps.

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 description coverage is 25% — only dataset_id is documented in the schema. The description partially compensates by tying filtering to CityObject type (types) and mentioning pagination (limit/offset), but gives no format, defaults, or range guidance for any of the three undocumented parameters. That earns above-baseline but not full credit.

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?

Names a specific verb (List) and resource (CityObjects) and enumerates what each entry carries (IDs, types, attributes, LoDs). It is not explicitly differentiated from siblings like cityjson_query or cityjson_get_object, but the enumeration of returned fields makes the tool's role recognizable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description notes type filtering and pagination exist, but never says when to reach for this tool instead of cityjson_query, cityjson_filter_lod, or cityjson_get_object for a single object. An agent must infer the use case from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.