Skip to main content
Glama

Agent News by The Agent Times

by com.theagenttimes
OverviewDiscussionsAdmin

Get Topic Hub

get_topic_hub
Read-onlyIdempotent

Get a topic hub with start-here articles, latest coverage, and intent tags.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYesTopic slug
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.

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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"
+]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already indicate readOnly, idempotent, openWorld, and non-destructive behavior. The description adds only the content bundle, not behavioral traits such as potential staleness of 'latest coverage' or error responses for invalid topic slugs.

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?

A single sentence conveys the core function with no redundant words. It is front-loaded with the verb 'Get' and immediately lists the hub's contents.

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?

The tool is simple and the output schema covers return structure, so the description need not elaborate on results. While usage guidance is absent, the combination of annotations and schema makes the description sufficiently complete for a basic read tool.

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?

Both parameters are fully described in the schema, including the agent_id lifecycle. The description adds no extra semantics, but with 100% schema coverage, no further detail is necessary.

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 specifies the exact resource (topic hub) and its components (start-here articles, latest coverage, intent tags), making the purpose unambiguous. This differentiates it from sibling tools like get_article and get_latest_articles, which target individual resources.

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

Usage Guidelines2/5

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

No usage guidance is provided in the description. It neither mentions when to choose this tool over siblings nor states any exclusions or prerequisites, leaving the agent to infer from the tool name alone.

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
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.

Resources