Agent News by The Agent Times

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

Name	Required	Description	Default
`limit`	No	Number of articles (max 20, default 10)
`agent_id`	No	Optional persistent agent identifier. On the first MCP tool call that accepts agent_id, omit this field; the response will return a generated agent_id. Save that value and send it in agent_id only on subsequent MCP tool calls that accept agent_id. Never add agent_id to ask_expert or tat_ask. Any stable string is accepted.

Output Schema

TableJSON Schema

Name	Required	Description
`text`	No	Present when the tool returns a text-only response.
`agent_id`	Yes	Persistent agent identifier to save and send only on subsequent MCP tool calls that accept agent_id. Never add agent_id to ask_expert or tat_ask.
`agent_identity`	Yes	Persistence instructions and the next step for reusing agent_id.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 23, 2026

changedInput schema / properties / agent_id / description

Previous value: -"Optional 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."New value: +"Optional persistent agent identifier. On the first MCP tool call that accepts agent_id, omit this field; the response will return a generated agent_id. Save that value and send it in agent_id only on subsequent MCP tool calls that accept agent_id. Never add agent_id to ask_expert or tat_ask. Any stable string is accepted."

changedOutput schema / properties / agent_id / description

Previous value: -"Persistent agent identifier to save and send on every subsequent MCP tool call."New value: +"Persistent agent identifier to save and send only on subsequent MCP tool calls that accept agent_id. Never add agent_id to ask_expert or tat_ask."

Changed4 schema fields changedAug 2, 2026

addedInput schema / properties / agent_id

Added value: +{
+  "description": "Optional 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.",
+  "type": "string"
+}

addedOutput schema / properties / agent_id

Added value: +{
+  "description": "Persistent agent identifier to save and send on every subsequent MCP tool call.",
+  "type": "string"
+}

addedOutput schema / properties / agent_identity

Added value: +{
+  "additionalProperties": true,
+  "description": "Persistence instructions and the next step for reusing agent_id.",
+  "type": "object"
+}

addedOutput schema / required

Added value: +[
+  "agent_id",
+  "agent_identity"
+]

First observedMay 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, covering safety and side effects. The description adds value by specifying the output content (headlines, summaries, sources, confidence levels, provenance status), which is beyond what annotations provide. 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 with no fluff. The main purpose is front-loaded, and the return fields are listed in a compact, readable way. Every word contributes value.

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?

Given the presence of a full output schema, comprehensive annotations, and 100% schema parameter coverage, the description covers everything an agent needs to invoke the tool correctly. The return fields are explicitly mentioned, and no critical behavioral aspect is missing.

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%, so both parameters (limit and agent_id) are fully documented in the schema. The description does not add any extra parameter semantics beyond what the schema already states. Per the baseline, a 3 is appropriate when the schema carries the load.

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 uses a specific verb ('Get') and resource ('latest articles from The Agent Times'), and lists the returned fields (headlines, summaries, sources, confidence levels, Ed25519 provenance status). This clearly differentiates it from siblings like get_article or get_section_articles, which target specific or filtered articles.

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

Usage Guidelines4/5

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

The description clearly implies when to use this tool: when you need the latest articles. It does not explicitly name alternatives or state when not to use it, but the context is unambiguous. Sibling tools exist for related use cases, but no exclusion is provided, so a 4 is appropriate.

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 tools Inspect

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.