Skip to main content
Glama

Agent Weather

by io.agentweather
OverviewDiscussionsAdmin

AI model directory index (free, day-old)

list_models
Read-onlyIdempotent

Free. Day-old index of the Agent Weather AI model directory: model id, name, vendor and categories only (models first seen at least 24 h ago; flagged in snapshot). Live prices, context length, vendor status, 24h/7d changes, job cost and events are in the paid get_model_report and get_model_category tools. Not a ranking. Supports filtering by vendor, category or text query and pagination (limit/offset). Use the ids with the paid get_model_report tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree-text filter on id/name
limitNoPage size (default 100, max 100)
offsetNoOffset for pagination
vendorNoFilter by vendor slug, e.g. openai
categoryNoFilter by category

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "reasoning",
-  "coding",
-  "vision-input",
-  "image-output",
-  "audio",
-  "retiring-soon",
-  "price-moved",
-  "free-tier"
-]New value: +[
+  "reasoning",
+  "coding",
+  "vision-input",
+  "image-output",
+  "audio",
+  "retiring-soon",
+  "free-tier"
+]
  2. 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 readOnlyHint/idempotentHint/openWorldHint, so the safety profile is covered; the description adds genuinely new behavior: the index is stale by design (models first seen at least 24h ago, flagged in `snapshot`) and excludes live pricing/status data. It does not mention rate limits, auth requirements, or result ordering, so it stops short of 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?

Front-loaded with the two decisive facts ('Free. Day-old'), then capabilities, then the sibling/data-boundary routing. No sentence is filler; the parenthetical about 24h/snapshot is the only detail that could be trimmed.

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?

There is no output schema, yet the description names the returned fields and the `snapshot` flag, and it warns what data will NOT be present versus the paid tools. For a free, read-only, filterable list tool that is sufficient to call it correctly and interpret the result.

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

Parameters3/5

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

Schema description coverage is 100% and every parameter (q, limit, offset, vendor, category) is already documented in the schema, including defaults and the max of 100. The description merely restates that filtering by vendor/category/text and pagination exist, adding no syntax or semantic detail beyond structured data — the baseline 3.

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?

States a specific verb+resource ('Free. Day-old index of the Agent Weather AI model directory') and enumerates exactly which fields come back (id, name, vendor, categories). It explicitly distinguishes itself from the paid siblings get_model_report and get_model_category, so an agent can route without opening any schema.

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?

Names the alternatives and the condition that selects them: live prices, context length, vendor status, changes, job cost and events 'are in the paid get_model_report and get_model_category tools.' It also states the downstream step ('Use the ids with the paid get_model_report tool') and a negative scoping caveat ('Not a ranking').

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

All Agent Weather toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources