Skip to main content
Glama

place_index

Read-only

What exists at a place, and when: dated stills, source quotes and measurements within radius_km of lat/lng or of an entity's site, newest first. Each row carries valid_on (world time) and recorded_at (our time). Filter by dates and kinds; paged. Metered: see CHARGING in the server instructions; quote first with billing_quote.

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

Input Schema

NameRequiredDescriptionDefault
idNoThe entity's numeric id (with entity_type).
latNoLatitude in decimal degrees, -90 to 90 (WGS84). With lng; or name an entity.
lngNoLongitude in decimal degrees, -180 to 180 (WGS84).
kindsNoComma list of row kinds: still, quote, verdict, match, measurement.
limitNoMaximum rows to return. 1-500. Default 100.
fieldsNoOnly these keys in each row (plus id). Omit for all.
offsetNoRows to skip, for paging. Default 0.
to_dateNoOnly rows valid on or before this date, YYYY-MM-DD.
from_dateNoOnly rows valid on or after this date, YYYY-MM-DD.
radius_kmNoRadius in km, up to 50. Default 2.
entity_typeNoEntity kind: deposit | infrastructure | company | project. With id, centres on that entity's site.
entity_typesNoComma list of entity kinds to include (deposit, infrastructure, company, project).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed22 schema fields changed
    • removedInput schema / properties / entity_type / default
      Removed value: -null
    • removedInput schema / properties / entity_type / title
      Removed value: -"Entity Type"
    • removedInput schema / properties / entity_types / default
      Removed value: -null
    • removedInput schema / properties / entity_types / title
      Removed value: -"Entity Types"
    • addedInput schema / properties / fields
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Only these keys in each row (plus id). Omit for all."
      +}
    • removedInput schema / properties / from_date / default
      Removed value: -null
    • removedInput schema / properties / from_date / title
      Removed value: -"From Date"
    • removedInput schema / properties / id / default
      Removed value: -null
    • removedInput schema / properties / id / title
      Removed value: -"Id"
    • removedInput schema / properties / kinds / default
      Removed value: -null
    • removedInput schema / properties / kinds / title
      Removed value: -"Kinds"
    • removedInput schema / properties / lat / default
      Removed value: -null
    • removedInput schema / properties / lat / title
      Removed value: -"Lat"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / lng / default
      Removed value: -null
    • removedInput schema / properties / lng / title
      Removed value: -"Lng"
    • removedInput schema / properties / offset / title
      Removed value: -"Offset"
    • removedInput schema / properties / radius_km / title
      Removed value: -"Radius Km"
    • removedInput schema / properties / to_date / default
      Removed value: -null
    • removedInput schema / properties / to_date / title
      Removed value: -"To Date"
    • removedInput schema / title
      Removed value: -"place_indexArguments"
    • removedOutput schema / title
      Removed value: -"place_indexDictOutput"
  2. Changed1 schema field changed
    • changedInput schema / properties / id / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  3. Changed11 schema fields changed
    • addedInput schema / properties / entity_type / description
      Added value: +"Entity kind: deposit | infrastructure | company | project. With id, centres on that entity's site."
    • addedInput schema / properties / entity_types / description
      Added value: +"Comma list of entity kinds to include (deposit, infrastructure, company, project)."
    • addedInput schema / properties / from_date / description
      Added value: +"Only rows valid on or after this date, YYYY-MM-DD."
    • addedInput schema / properties / id / description
      Added value: +"The entity's numeric id (with entity_type)."
    • addedInput schema / properties / kinds / description
      Added value: +"Comma list of row kinds: still, quote, verdict, match, measurement."
    • addedInput schema / properties / lat / description
      Added value: +"Latitude in decimal degrees, -90 to 90 (WGS84). With lng; or name an entity."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum rows to return. 1-500. Default 100."
    • addedInput schema / properties / lng / description
      Added value: +"Longitude in decimal degrees, -180 to 180 (WGS84)."
    • addedInput schema / properties / offset / description
      Added value: +"Rows to skip, for paging. Default 0."
    • addedInput schema / properties / radius_km / description
      Added value: +"Radius in km, up to 50. Default 2."
    • addedInput schema / properties / to_date / description
      Added value: +"Only rows valid on or before this date, YYYY-MM-DD."
  4. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely new behavior: newest-first ordering, offset/limit paging, metered charging governed by server instructions, and the presence of both valid_on (world time) and recorded_at (our time) per row. It stops short of describing cost magnitude or error/empty-result behavior.

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

Conciseness5/5

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

Two sentences, densely packed but zero waste: content, anchor mode, ordering, row timestamps, filters, paging and metering each get a clause and the core purpose is front-loaded.

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 12-parameter, zero-required tool with a full output schema and complete annotations, the description covers the dual anchoring modes, ordering, paging, metering workflow and temporal semantics. Remaining specifics (radius default and cap, per-kind enum values) live in the schema, so nothing critical is missing, though the ambiguity of passing neither coordinates nor entity could have been addressed.

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 baseline is 3. The description does add value by explaining that the spatial anchor is either lat/lng or an entity's site (id + entity_type), which is a relationship the schema documents only piecemeal, and it clarifies date filtering semantics. But it adds no detail on kinds, fields projection, or limit/offset beyond what the schema already says.

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 states a concrete resource and scope: dated stills, quotes and measurements within a radius of a lat/lng or an entity's site, returned newest first. That is specific enough to distinguish it from generic listing tools, but it never names a sibling (e.g. nearby, signals, look_at), so the boundary is left to inference.

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?

It gives clear operating context: filter by dates and kinds, results are paged, and the call is metered so the agent must quote first with `billing_quote`. That is a real prerequisite that changes how the tool is invoked. It does not, however, say when to prefer a sibling such as `nearby` or `map_viewport` instead.

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