list_elevatedList only the volcanoes currently above Normal/Green status (i.e., elevated unrest or eruption). Smallest practical fingerprint of "what's happening right now."
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| note | Yes | Description of elevated status criteria | |
| count | Yes | Number of elevated volcanoes | |
| volcanoes | Yes | List of volcanoes above Normal/Green status |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {}
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "count": {
+ "description": "Number of elevated volcanoes",
+ "type": "number"
+ },
+ "note": {
+ "description": "Description of elevated status criteria",
+ "type": "string"
+ },
+ "volcanoes": {
+ "description": "List of volcanoes above Normal/Green status",
+ "items": {
+ "properties": {
+ "alert_level": {
+ "description": "Current alert level (Advisory/Watch/Warning)",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "alert_message": {
+ "description": "Current alert status message",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "alert_url": {
+ "description": "URL to full alert information",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "color_code": {
+ "description": "Aviation color code (Yellow/Orange/Red)",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "elevation_m": {
+ "description": "Elevation in meters",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "latitude": {
+ "description": "Volcano latitude",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "longitude": {
+ "description": "Volcano longitude",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "modified": {
+ "description": "Last modification timestamp",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "name": {
+ "description": "Volcano name",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "observatory": {
+ "description": "Observatory code (AVO, CVO, HVO, etc.)",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "slug": {
+ "description": "USGS volcano slug for URLs",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "synonyms": {
+ "description": "Alternative volcano names",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "vnum": {
+ "description": "USGS volcano number",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "count",
+ "note",
+ "volcanoes"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover readOnlyHint, idempotentHint, destructiveHint. Description adds 'smallest practical fingerprint' hinting at lightweight nature, but no contradictions. Adequate but minimal extra value.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no waste, front-loaded with key information. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No parameters, output schema exists, description fully explains return content. Complete for a simple filtered list tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters; schema coverage 100%. Description adds context about what is listed (elevated status) beyond schema, meeting the baseline for zero parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it lists volcanoes above Normal/Green status, with verb 'list' and specific resource. Distinguishes from siblings like list_volcanoes by focusing on elevated status only.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implicitly indicates used for a quick snapshot of current unrest. Does not explicitly state when not to use, but context of sibling tools and clarity of purpose compensate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.