Skip to main content
Glama

get_area_geology

Read-onlyIdempotent

Retrieve geological map legends for a WGS84 bounding box up to 0.25° tall and wide, enabling users to identify geology in a specific area.

Instructions

List geological map legends in a WGS84 box up to 0.25° tall and wide.

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": {
      "south": "<south>",
      "west": "<west>",
      "north": "<north>",
      "east": "<east>"
    },
    "name": "get_area_geology"
  }
}

Input Schema

NameRequiredDescriptionDefault
eastYes
westYes
limitNo
northYes
southYes
offsetNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare this a read-only, idempotent, non-destructive, open-world query, so the safety profile is covered. The description usefully adds the size constraint that is not expressed in the schema. It does not disclose what happens when the 0.25° limit is exceeded or how results are ordered, which are the remaining behavioral unknowns.

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?

A single sentence with no filler, front-loading the verb, resource, and constraint. Nothing is redundant, though the terseness shifts the cost onto other dimensions.

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

Completeness2/5

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

An output schema exists, so return values need not be described, but for a six-parameter tool with zero schema description coverage the definition is too thin: pagination, the consequences of exceeding the box-size cap, and differentiation from get_geology are all absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden. It conveys that south/west/north/east form a WGS84 bounding box, which is genuinely useful, but it says nothing about the limit (default 25, max 100) or offset pagination parameters, leaving a third of the parameters unexplained anywhere.

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 gives a specific verb ('List') and resource ('geological map legends') plus a spatial scope ('WGS84 box up to 0.25° tall and wide'), which is concrete enough to act on. It does not compare itself to the sibling get_geology, so an agent must guess whether legends are a subset or a different granularity, which keeps it below a 5.

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?

Usage is only implied: the 'up to 0.25° tall and wide' cap tells the agent this is for small areas, and the WGS84 mention hints at coordinate expectations. There is no explicit statement of when to prefer this over get_geology or what to do when the requested area exceeds the cap (error? truncation?).

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