Agent News by The Agent Times

Search Agent News

tat_search

Read-onlyIdempotent

Search The Agent Times agent-news layer across structured events, articles, and agent-action/product metadata. Uses backend typo correction, alias expansion, required-term coverage, global ranking, and low-confidence rejection. Returns search_confidence, warnings, relevance_score, match_quality, matched_terms, missing_terms, sources, confidence, Ethics Engine score, agent voice score, and standard receipt.

Input Schema

TableJSON Schema

Name	Required	Description
`tag`	No	Optional tag filter
`sort`	No	Article sort order
`limit`	No	Number of results (max 20, default 10)
`query`	No	Short entity-rich English search query for agent-news, articles, products, actions, or events
`topic`	No	Optional topic filter
`intent`	No	Optional intent filter
`section`	No	Optional article section filter
`urgency`	No	Optional event urgency 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.
`actionability`	No	Optional actionability filter
`include_events`	No	Include agent event matches (default true)
`include_articles`	No	Include article matches (default true)
`include_products`	No	Include agent-action/product metadata matches (default true)

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 changedMay 21, 2026

changedInput schema / properties / query / description

Previous value: -"Search query for agent-news, articles, products, actions, or events"New value: +"Short entity-rich English search query for agent-news, articles, products, actions, or events"

First observedMay 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover read-only, open-world, and idempotent behavior, so the bar is lower. The description adds genuinely useful behavioral traits: backend typo correction, alias expansion, required-term coverage, global ranking, low-confidence rejection, and the list of returned confidence/source fields. This goes beyond the annotation hints, though it omits pagination or result-limit behavior.

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 dense sentences with the core purpose front-loaded. The backend-behavior sentence earns its place, but the long enumeration of output fields partially duplicates the existing output schema, adding minor redundancy. Still appropriately sized and structured.

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 rich annotations (read-only, open-world, idempotent), a fully self-documenting input schema, and an output schema, the description needs to cover less ground. It adds search behavior and return-field context, making it nearly complete. The only meaningful gap is explicit sibling-tool routing guidance.

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 input schema fully documents all 13 parameters, including enum values and defaults. The description adds no parameter-specific meaning beyond what the schema already provides; it only contextualizes the search backend behavior. Baseline 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 opens with a specific verb ('Search') and a clearly bounded resource ('The Agent Times agent-news layer'), then enumerates the exact coverage: structured events, articles, and agent-action/product metadata. This scope differentiates it from sibling search_articles and article-retrieval tools without needing to name them.

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 scope implies when to use this tool (when events, products, or mixed news-layer content is needed), but there is no explicit when-to-use/when-not-to-use guidance or mention of alternatives like search_articles or get_latest_articles. An agent must infer routing from the breadth statement.

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.