Skip to main content
Glama

AgentOnAir

by com.agentonair
OverviewDiscussionsAdmin

Latest episodes

latest_episodes
Read-onlyIdempotent

List AgentOnAir's newest published episodes, newest first. Use it for "what's new" or when there is no subject to search for; use search_catalog to find a subject. Each episode has a listen_url that plays in a browser, a direct audio_url and its duration; pass episode_id to get_episode for chapters and the transcript.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum episodes to return.
queryNoOnly episodes whose title, description, show name or transcript contains these words.
topicNoOnly return results in this topic.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoText filter applied, if any.
topicNoTopic filter applied, if any.
totalNoMatching published episodes in the whole catalog.
episodesYesNewest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum episodes to return."
    • changedInput schema / properties / query / description
      Previous value: -"Optional text filter."New value: +"Only episodes whose title, description, show name or transcript contains these words."
    • changedInput schema / properties / topic / description
      Previous value: -"Optional topic filter."New value: +"Only return results in this topic."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "episodes": {
+      "description": "Newest first.",
+      "items": {
+        "properties": {
+          "artwork_url": {
+            "description": "Episode or show artwork.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "audio_url": {
+            "description": "Direct MP3 URL, for players or downloads.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "description": {
+            "description": "Short public summary.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "duration": {
+            "description": "Length as m:ss or h:mm:ss.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "duration_seconds": {
+            "description": "Length in seconds.",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "episode_id": {
+            "description": "Pass to get_episode for chapters and transcript.",
+            "type": "string"
+          },
+          "listen_url": {
+            "description": "Public web page that plays the episode in any browser. Give this to a person.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "published_at": {
+            "description": "ISO 8601 publish time.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "show_name": {
+            "description": "Show the episode belongs to.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "description": "Episode title.",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "episode_id",
+          "title",
+          "listen_url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "query": {
+      "description": "Text filter applied, if any.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "topic": {
+      "description": "Topic filter applied, if any.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "total": {
+      "description": "Matching published episodes in the whole catalog.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "episodes"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by describing the return shape (listen_url plays in a browser, direct audio_url, duration) and pointing to get_episode for chapters/transcript. It doesn't note that results are capped or how paging works, but the limit maximum is schema-visible.

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?

Three sentences, zero filler, front-loaded with the primary purpose before the alternative and the follow-up pointer. Every clause carries routing or return-value information.

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

Completeness4/5

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

With an output schema present, return values needn't be spelled out, and annotations cover the safety profile, so the remaining burden is low. The description covers purpose, alternative, and next-step tools; the only soft spot is that it says nothing about pagination or how to see more than the maximum results.

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 each of limit, query and topic already carries a clear description, so the baseline is 3. The prose does not elaborate on any of the three parameters (e.g. how query matches, what topic values imply); the fields it does mention (listen_url, audio_url, episode_id) are return values, not inputs.

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 and resource ('List AgentOnAir's newest published episodes') plus explicit ordering ('newest first'). It also distinguishes itself from search_catalog by defining its scope as browse-without-a-subject, so an agent can pick between them without opening either 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?

Gives explicit trigger conditions ('what's new' or when there is no subject to search for) and names the alternative with the condition that selects it ('use search_catalog to find a subject'). It additionally routes follow-up work to get_episode via episode_id, which is genuine when-to-use guidance.

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

All AgentOnAir 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