Skip to main content
Glama
Sign In
@terranode-co/mcp-server

@terranode-co/mcp-server

Official
by terranode-co
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

check_location

Find which polygon feature contains a specific coordinate by submitting latitude, longitude, and a dataset UUID. Returns matching feature properties or indicates no match.

Instructions

Check which feature in a polygon dataset contains a given coordinate (point-in-polygon query). Returns the properties of all matching features, or indicates no match. Requires latitude, longitude, and a dataset id (UUID) from list_datasets. Call list_datasets first to get the id. This is NOT a geocoder — it requires numeric coordinates, not addresses or place names.

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": {
      "lat": "<lat>",
      "lng": "<lng>",
      "dataset": "<dataset>"
    },
    "name": "check_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesLatitude in decimal degrees (WGS84). Example: 40.7128
lngYesLongitude in decimal degrees (WGS84). Example: -74.0060
datasetYesDataset id (UUID) from list_datasets

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.10

TDQS

A4.2/5.0
Behavior3/5

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

Describes return behavior ('Returns properties of all matching features, or indicates no match') but does not disclose potential side effects or permission requirements. Since no annotations are provided, the description carries the full burden, and it falls short of fully disclosing operational traits.

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?

Three efficient sentences: first defines purpose, second describes output, third states requirements and disclaimers. Front-loaded with the core action, no wasted 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?

Given no output schema, it adequately describes the return value. For a simple point-in-polygon query with three parameters, it covers inputs, prerequisites, and what to expect. Minor gap: no mention of error handling or output data format.

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 baseline is 3. The description adds minimal extra meaning beyond the schema, only noting that the dataset id comes from list_datasets. No additional constraints or examples beyond what is in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear verb+resource ('check which feature in a polygon dataset contains a given coordinate') and explicitly distinguishes from siblings by stating it is NOT a geocoder and requires numeric coordinates, making its purpose unambiguous.

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

Usage Guidelines5/5

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

Explicitly states prerequisites (call list_datasets first to get the dataset id) and provides a clear when-not-to-use condition (not for addresses or place names), guiding appropriate usage against alternatives.

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

Deploy Server

Other Tools