Agent News by The Agent Times

Search Articles

search_articles

Read-onlyIdempotent

Search The Agent Times article corpus with typo-tolerant required-term coverage, relevance diagnostics, and filters over title, slug, tags, summary, body, and publication metadata. Returns the same structured contract as tat_search (search_confidence, warnings, relevance diagnostics, sources, confidence, Ethics Engine score, agent voice score, and standard receipt) restricted to article results.

Input Schema

TableJSON Schema

Name	Required	Description
`tag`	No	Optional tag filter
`sort`	No	Sort order
`limit`	No	Number of results (max 20)
`query`	No	Search query
`topic`	No	Optional topic filter
`intent`	No	Optional intent filter
`section`	No	Optional section filter
`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.
`published_after`	No	ISO date lower bound
`published_before`	No	ISO date upper bound

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 18, 2026

removedInput schema / properties / offset

Removed value: -{
-  "description": "Offset for pagination",
-  "type": "integer"
-}

First observedMay 11, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover readOnly, openWorld, idempotent, and non-destructive behavior, and the description adds non-obvious behavior: typo-tolerant required-term coverage, relevance diagnostics, and the exact structured receipt fields. It does not contradict annotations, and no destructive behavior is implied.

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 sentences of dense, front-loaded prose: purpose first, matching semantics second, return contract third. No filler or repetition of schema details.

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 10-parameter read-only search tool, the description plus a fully documented schema and output schema cover behavior, return shape, and filtering scope. It leaves explicit selection guidance to the usage dimension and does not restate schema details, which is appropriate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds useful meaning by saying filters span title, slug, tags, summary, body, and publication metadata and that matching is typo-tolerant with required-term coverage. This contextualizes the query and filter parameters beyond their individual schema descriptions.

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 names the exact verb ('Search'), the resource ('The Agent Times article corpus'), and the distinguishing scope ('restricted to article results') relative to tat_search. It also enumerates filter targets and the return contract, so an agent can tell it apart from generic search or retrieval siblings.

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?

It positions this tool as the article-corpus search variant and explicitly references tat_search's contract as the return shape, signaling article-only scope versus the general tat_search. It does not explicitly state when-not-to-use sibling retrieval tools like get_latest_articles or get_section_articles, but the search/filter framing gives clear context.

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.