Skip to main content
Glama

get_geology

Read-onlyIdempotent

Reads the GSJ 1:200,000 geological map legend for a WGS84 latitude and longitude point in Japan, helping identify local geological units from coordinates.

Instructions

Read the GSJ 1:200,000 geological map legend at a WGS84 point in Japan.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "get_geology"
  }
}

Input Schema

NameRequiredDescriptionDefault
latitudeYes
longitudeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world behavior, so the bar is lower. The description adds genuinely useful context beyond them: the dataset provenance and scale (GSJ 1:200,000), which conveys resolution limits, and the Japan-only coverage plus WGS84 datum requirement.

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?

One sentence, front-loaded with the verb and dataset, with the spatial constraint appended last. No wasted wording and nothing important buried.

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 simple two-parameter lookup with an output schema and full annotation coverage, the description covers scope, datum, and dataset resolution adequately. Only a brief note on what the legend returns or its limitations would make it fully complete.

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?

Schema coverage is 0%, but the two parameters are self-describing latitude/longitude fields with explicit min/max bounds. The description still adds meaning the schema lacks by specifying the WGS84 datum and that the point must fall in Japan, which prevents datum confusion and out-of-scope calls.

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 specific verb (read) and resource (GSJ 1:200,000 geological map legend) and bounds it to a WGS84 point in Japan, which contrasts implicitly with area-based siblings like get_area_geology. It stops short of naming any sibling directly, so differentiation is inferable rather than explicit.

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 'at a WGS84 point in Japan' implies the point-lookup use case and the geographic scope, but there is no explicit when-to-use versus when-not guidance and no mention of alternatives for area queries or non-Japan coordinates. Usage is implied rather than stated.

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