Skip to main content
Glama

Agent News by The Agent Times

by com.theagenttimes

Get Latest Articles

get_latest_articles
Read-onlyIdempotent

Get the latest articles from The Agent Times. Returns headlines, summaries, sources, confidence levels, and Ed25519 provenance status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of articles (max 20, default 10)
agent_idNoOptional persistent agent identifier. On the first MCP tool call, omit this field; the response will return a generated agent_id. Save that value and send it in agent_id on every subsequent MCP tool call. Any stable string is accepted.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoPresent when the tool returns a text-only response.
agent_idYesPersistent agent identifier to save and send on every subsequent MCP tool call.
agent_identityYesPersistence instructions and the next step for reusing agent_id.

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, idempotentHint=true). The description adds meaningful behavioral context by specifying the returned data elements, including the Ed25519 provenance status, which is not disclosed in annotations. There is no contradiction with annotations.

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 two concise sentences that front-load the purpose and immediately follow with what the tool returns. No wasted words or redundancy.

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?

Given the presence of an output schema and strong annotations, the description is sufficiently complete. It explains the tool's purpose and output, though it does not clarify the definition of 'latest' (e.g., publication date ordering), which is a minor gap.

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 descriptions cover 100% of parameters (limit and agent_id), including defaults and the agent_id lifecycle. The description itself adds no parameter-specific semantics beyond what the schema provides, so the baseline of 3 is appropriate.

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 clearly states a specific verb ('Get') and resource ('latest articles from The Agent Times'), and enumerates the return fields (headlines, summaries, sources, confidence levels, Ed25519 provenance status). This distinguishes it from sibling tools like get_article or search_articles.

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 description implies usage for retrieving recent articles but does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or alternative tools for search or specific article retrieval. Guidance is present but only implied.

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

All Agent News by The Agent Times 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

B3.4/5.0
Disambiguation2/5

ask_expert and tat_ask have identical descriptions for the same function, creating direct overlap. tat_search and search_articles also cover similar search territory with unclear boundaries. Other tools like get_latest_articles and get_section_articles are distinct but the duplication undermines clear separation.

Naming Consistency2/5

Naming mixes a 'tat_' prefix on many tools (tat_search, tat_recommend) but leaves others without it (ask_expert, get_article, list_topics). The inconsistency is not systematic; some verbs like 'ask' vs 'tat_ask' are redundant while others like 'get_' and 'search_' are used in both prefixed and unprefixed forms.

Tool Count3/5

20 tools is on the heavier end for a news server; while the domain (news aggregation, search, trust metrics, comments) seems broad enough to justify many tools, the presence of duplicate tools (ask_expert/tat_ask) inflates the count unnecessarily. A trimmed set around 15 would be more appropriate.

Completeness3/5

The tool set covers core news retrieval (articles, sections, topics), search, trust/provenance, events, comments, and usage reporting. Notable gaps include user-specific features (subscriptions, saved articles) and administrative tools. The duplication suggests an unclear boundary between the agent-news layer and static news, leaving some workflows ambiguous.

Resources