Skip to main content
Glama

Emergent.FM

Entries of one day

items_by_date
Read-only

Every published entry of one day (New York time): that day's show items, its newsroom stories and its wire rows. Covers the feed's last 30 shows, six weeks of stories and at most 500 wire rows.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "<date>"
    },
    "name": "items_by_date"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesA day in New York time, YYYY-MM-DD, for example 2026-11-17.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavioral context that annotations cannot: the data is silently bounded — last 30 shows, six weeks of stories, at most 500 wire rows — warning the agent about truncation and limited historical reach.

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?

Two dense sentences with zero filler — the scope and content types come first, the coverage limits second. Every clause carries information an agent needs.

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?

For a one-parameter read tool with full annotation coverage and no output schema, the definition supplies scope, timezone and retention limits. The only gap is that it does not hint at the shape of a returned entry, though no output schema exists for the description to defer to.

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 coverage is 100% and the single 'date' parameter already documents the YYYY-MM-DD format and New York timezone. The description only restates the timezone, adding no new meaning; baseline 3 applies when the schema does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and scope: 'Every published entry of one day (New York time)' and enumerates the three content classes returned (show items, newsroom stories, wire rows). That is far more informative than the title, though it never names a sibling such as search_items or latest_items to draw the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied — the day-scoped framing suggests this is for pulling a complete single-day digest rather than the latest items or a keyword search, but no explicit when-to-use or when-not guidance is given and no alternative is named.

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