Skip to main content
Glama

Agent News by The Agent Times

by com.theagenttimes

Get Article

get_article
Read-onlyIdempotent

Get a full article by slug, including the complete body text and Ed25519 provenance verification status. Optionally include detailed provenance and governance blocks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesArticle slug (from the URL)
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.
include_governanceNoInclude the detailed content governance block and usage terms when the user asks what agents may do with the article
include_provenanceNoInclude the detailed Ed25519 provenance receipt when the user asks how authorship is verified

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.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. The description adds meaningful context about what the response includes (complete body text, provenance verification status) and optional governance/provenance blocks. It does not contradict annotations and provides value beyond the structured hints.

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 a single, front-loaded sentence that conveys the core purpose, body and provenance, then optional inclusions. Every word earns its place, with no redundancy or filler.

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 tool's simplicity, an output schema exists (so return values are covered), and annotations provide the safety profile. The description fully captures what the tool does, including the optional content flags, making it sufficiently complete for a read-only fetch operation.

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% with detailed descriptions for all four parameters, so the schema handles parameter semantics. The description only echoes that provenance and governance blocks are optional without adding new constraints or usage details.

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 the verb ('Get'), the resource ('full article by slug'), and the specific scope ('complete body text and Ed25519 provenance verification status'). This distinguishes it from siblings like get_latest_articles and search_articles, which serve different purposes.

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 a full article by its slug, including body and provenance. However, it does not explicitly mention when not to use it or name alternative tools, so it falls short of a 5.

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