Agent News by The Agent Times

Get Section Articles

get_section_articles

Read-onlyIdempotent

Get articles from a specific section. Each article includes Ed25519 provenance status. Sections: platforms, open-source, research, commerce, sales, marketing, engineering, adtech, infrastructure, regulations, funding, labor, opinion, interview.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Number of articles (max 20, default 10)
`section`	Yes	Section name
`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"
+]

Changed1 schema field changedJun 26, 2026

changedInput schema / properties / section / enum

Previous value: -[
-  "platforms",
-  "open-source",
-  "research",
-  "commerce",
-  "sales",
-  "marketing",
-  "engineering",
-  "adtech",
-  "infrastructure",
-  "regulations",
-  "funding",
-  "labor",
-  "opinion"
-]New value: +[
+  "platforms",
+  "open-source",
+  "research",
+  "commerce",
+  "sales",
+  "marketing",
+  "engineering",
+  "adtech",
+  "infrastructure",
+  "regulations",
+  "funding",
+  "labor",
+  "opinion",
+  "interview"
+]

First observedMay 11, 2026

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 (readOnlyHint, idempotentHint, non-destructive). The description adds the useful behavioral detail that each article includes Ed25519 provenance status, which is not present in the annotations and helps set expectations about the response content. It could mention auth or rate limits, but the annotation coverage lowers the burden.

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?

The description is compact: one sentence states the core action, one adds the provenance detail, and the section list is informative despite being long. The list is somewhat redundant with the schema enum, but the description is still well-structured and front-loaded.

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 simple read-only tool with full schema coverage and an output schema, the description is sufficient. It adds the provenance context and lists all valid sections. It does not discuss pagination or error handling, but the output schema and annotations cover most operational needs.

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 the schema already fully documents all three parameters. The description's list of valid sections merely duplicates the enum in the schema and adds no new semantic detail about limit or agent_id, so it stays at the baseline.

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?

The description states a specific verb and resource ('Get articles from a specific section') and enumerates the valid section values, which makes the tool's purpose immediately clear. It does not explicitly contrast with sibling tools like get_latest_articles or get_related_articles, so it misses the top score for differentiation.

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: use this when you need articles from a particular named section. However, it provides no explicit guidance about when not to use it or which alternatives (e.g., get_latest_articles, search_articles) would be more appropriate in other contexts, so usage guidance is 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 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.