Skip to main content
Glama

Abstraxn Agent Layer

by io.github.sandeep-antier

Weather forecast and current conditions

weather.forecast
Read-onlyIdempotent

Weather data from a global weather data provider — current conditions, short-range forecast, astronomy, historical, marine, and location search. Free, read-only, no wallet needed. Every action requires q, a location: a city name (e.g. "Paris"), "lat,lon" (e.g. "48.85,2.35"), a US/UK/Canadian postal code, or an IATA airport code. Pick one action:

  • current: current conditions for q. Optional aqi (default false) adds basic air quality data.

  • forecast: forecast for q. Optional days — this deployment runs on a data plan capped at 3 days, so only 1-3 is accepted; omit for the provider default. Optional aqi, alerts (default false, adds active weather alerts for the location where available).

  • astronomy: sunrise/sunset/moonrise/moonset/moon phase for q on date (required, YYYY-MM-DD).

  • search: resolve a fuzzy q into matching locations (name, region, country, lat/lon) — use this first if you only have an approximate place name and need to disambiguate.

  • history: past weather for q on date (required, YYYY-MM-DD, must be yesterday). This deployment enforces a free-tier data plan that only allows yesterday's date — any other date is rejected before a provider call is made.

  • marine: marine/sailing conditions for q. This deployment runs on a data plan limited to 1 day of data with no tide information.

Results are for general informational purposes only — do not use them as the sole basis for decisions involving personal safety, aviation, marine navigation, or emergency planning.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesLocation: city name, "lat,lon", postal code, or airport code. Required for every action.
aqiNocurrent / forecast / history: include basic air quality data (default false).
dateNoastronomy / history: date in YYYY-MM-DD format. Required for both.
daysNoforecast: number of forecast days (1-3 on this deployment's plan). Omit for the provider default.
actionYesWhich weather operation to perform.
alertsNoforecast: include active weather alerts for the location (default false).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
messageNo

TDQS

A5/5.0
Behavior5/5

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

Beyond the read-only annotation, it discloses deployment-specific limits: forecast capped at 3 days, history restricted to yesterday, marine limited to 1 day with no tides, and rejection before a provider call. It adds a safety disclaimer that results must not be used for aviation, marine navigation, or emergency planning.

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 description is long but earns its length: a one-sentence overview, a clear `q` rule, and six bulleted actions with their constraints. It is front-loaded and has no filler; every sentence conveys an operational requirement or caveat.

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?

With six parameters, six actions, an output schema, and deployment plan caps, the description covers all details an agent needs to select and invoke correctly. It explains date restrictions, defaults, and safety caveats, so the output schema handles return values and the description handles behavior.

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

Parameters5/5

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

Schema coverage is 100%, yet the description adds substantial meaning: accepted `q` formats (city, lat,lon, postal code, IATA), per-action parameter applicability, defaults, and server-side constraints. It clarifies which params matter for which action, going far beyond the schema's basic field descriptions.

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 opens by identifying the tool's domain and capabilities: 'Weather data from a global weather data provider — current conditions, short-range forecast, astronomy, historical, marine, and location search.' It enumerates six concrete actions, which is specific and clearly separates it from non-weather sibling tools.

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?

It gives explicit per-action guidance and even directs the agent to use `search` first when only an approximate place name exists. It also states constraints like 'history ... must be yesterday' and notes when to omit `days`, making when-to-use unambiguous.

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

All Abstraxn Agent Layer toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Tools are broadly distinct by domain (market, network, social, travel, web3), but some overlap exists between market.crypto and network.token_price (both provide token prices), and between network.token_info and web3.lookup's token_metadata action. However, the descriptions clarify the differences well.

Naming Consistency3/5

Tool names use a domain.subdomain pattern (e.g., market.crypto, network.gas_info), but the subdomains mix styles: dots (market.crypto), underscores (network.token_info), and plain names (travel.search). Additionally, actions within tools like 'places.lookup' have inconsistent naming (text_search_full vs. solar_building_insights).

Tool Count4/5

With 11 tools covering diverse domains (crypto, network, places, social, travel, web3), the count is reasonable. However, some tools encapsulate many actions (e.g., market.crypto has 6 actions, places.lookup has 12), hinting at a slightly heavy surface, but overall it fits the broad scope.

Completeness4/5

The tool set covers core workflows for each domain: crypto market data, network operations (block, gas, transfers, tokens), place search, social profile lookup, travel search, and web3 lookups. Minor gaps exist (e.g., no tool for sending transactions or managing user accounts), but the stated purpose (agent layer for diverse tasks) is mostly fulfilled.

Resources