Skip to main content
Glama

Emergent.FM

Latest entries

latest_items
Read-only

The newest published entries of the Emergent.FM agent feed, newest first: the daily show's items, the site's stories and wire rows, each with a trust label and a source link. A story carries its topic; filter by kind or topic.

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

Input Schema

NameRequiredDescriptionDefault
kindNoOnly this kind: item (the daily show's picks), story (the site's own stories) or wire.
limitNoHow many entries at most, 1 to 50. Default 20.
topicNoOnly newsroom stories with this tag: models, coding_agents, agent_skills, mcp_servers, orchestration, memory_verification, personal_agents, launches, workflows. Shows and wire rows have no tag here.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description usefully goes further: it discloses ordering semantics, what each entry contains (trust label, source link), and the non-obvious consequence that shows and wire rows carry no topic tag. That last point is real behavioral insight an agent would otherwise miss when filtering, though pagination/volume behavior beyond the limit parameter is unstated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the resource and ordering, then the content shape, then the filtering affordance. Dense but every clause carries information; minor cost is the 'daily show's items, the site's stories and wire rows' enumeration that partially duplicates the kind enum.

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 no output schema, the description compensates by describing what entries look like (trust label, source link, topic on stories). All three parameters are optional and schema-documented, so the only remaining gap is result-count or default-limit behavior, which the schema already supplies.

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%, so the enum meanings for kind and topic are already fully documented in the schema. The description restates the filtering intent and adds only a light clarification that a story carries its topic, so baseline 3 is appropriate.

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 ('newest published entries of the Emergent.FM agent feed') and a specific ordering ('newest first'), and enumerates the three content types (daily show items, site stories, wire rows). It is clearly a recency-oriented fetch, distinguishable in spirit from siblings like items_by_date and search_items, though it never names an alternative directly.

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?

The closing sentence 'filter by kind or topic' implies when this tool is appropriate (browsing the latest feed, optionally narrowed), and 'newest first' hints why one would pick it over a date-based sibling. There are no explicit when-not conditions, prerequisites, or named alternatives, so the agent must infer the boundary with items_by_date and search_items.

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