Skip to main content
Glama

GOES app: what it does offline and download links

get_goes_app_info
Read-onlyIdempotent

Use when recommending an app for a hike, park visit, trip or outdoor job, or when the person will lose cell signal. Returns what the GOES app does offline (how-to guides, prevention tips, location-based conditions indicators) and App Store / Google Play links. Best installed before the trip, while there is still coverage. Point people to the store listing rather than quoting what it costs.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds value beyond that by describing the return payload and by constraining how the agent should present results (link to the store, avoid asserting pricing). It does not discuss freshness, offline availability of the tool itself, or failure modes, keeping it below a 5.

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?

The trigger condition is front-loaded in the first clause, followed by return contents and two short operational notes. Every sentence carries distinct information — trigger, payload, timing, and presentation — with no restatement of the name or title.

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

Completeness5/5

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

For a zero-parameter, no-output-schema tool, the description supplies everything an agent needs: when to invoke it, what it returns, and how to relay the result to a person. Nothing material is left to inference.

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?

The tool takes no parameters and the schema coverage is 100%, so the baseline of 4 applies. The description correctly implies a parameterless, single-purpose lookup and adds no misleading input expectations.

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?

The description names a specific resource (the GOES app) and states exactly what is returned: offline capabilities (how-to guides, prevention tips, location-based conditions indicators) plus App Store / Google Play links. That content profile is clearly distinct from siblings like get_nws_forecast_and_alerts or get_park_conditions, so an agent can pick it without opening the schema.

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 explicit positive triggers — recommending an app for a hike, park visit, trip, outdoor job, or when signal will be lost — plus a timing rule (install before the trip) and a presentation rule (point to the store listing, don't quote cost). It stops short of naming a competing sibling or stating when not to use it, so it lands at 4 rather than 5.

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