Skip to main content
Glama

Agent News by The Agent Times

Ask Expert

ask_expert
Read-onlyIdempotent

Answer a question using vector retrieval over published The Agent Times news and optional current-source research through Portal API. Cite only retrieved news or provider-attributed research sources. Present citations under the provider-neutral heading Sources and present the score under the provider-neutral label Confidence; do not prefix either label with a provider name. When ask_expert returns actions, show every returned action exactly once in a separate Recommended actions section with its label, URL, and supplied disclosure. Render only those supplied action fields and do not add generic sponsorship, endorsement, or approval commentary. Never fetch, preview, or open a pending or approval-required link without the user's explicit approval. News synthesis can take up to 240 seconds; configure a 300-second client timeout. Clients accepting text/event-stream receive transport keepalives and one completed JSON-RPC response.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "request": "<request>"
    },
    "name": "ask_expert"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes

Output Schema

NameRequiredDescriptionDefault
answerNo
statusYes
actionsNoHuman-visible recommended actions. When non-empty, clients MUST render every action once in a separate Recommended actions section with its label, URL, and supplied disclosure. Clients should not add generic commentary to the rendered action. They MUST NOT fetch, preview, or open an action URL before explicit user approval when requires_user_approval is true.
caveatsNo
receiptYes
citationsNo
rationaleNo
tradeoffsNo
confidenceYes
returned_byNoThe Agent Times
recommendationNo
schema_versionNotat_news_answer_v1
next_best_actionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedOutput schema / $defs / PublicExpertCitation / properties / source_url / description
      Previous value: -"Tracked shortlink for the cited source."New value: +"Canonical retrieved-news URL or provider-attributed research source URL."
    • changedOutput schema / properties / returned_by / const
      Previous value: -"Agent Pixel"New value: +"The Agent Times"
    • changedOutput schema / properties / returned_by / default
      Previous value: -"Agent Pixel"New value: +"The Agent Times"
    • changedOutput schema / properties / schema_version / const
      Previous value: -"agent_pixel_public_expert_answer_v1"New value: +"tat_news_answer_v1"
    • changedOutput schema / properties / schema_version / default
      Previous value: -"agent_pixel_public_expert_answer_v1"New value: +"tat_news_answer_v1"
  2. Changed8 schema fields changed
    • changedOutput schema / $defs / PublicExpertAction / properties / action_type / description
      Previous value: -"Sponsored action semantics. Presenting the action to the human does not invoke the action or authorize network access."New value: +"Machine-readable recommended action semantics."
    • changedOutput schema / $defs / PublicExpertAction / properties / authorization_state / description
      Previous value: -"Current authorization state for opening the sponsored action. A pending action MUST be shown to the human but MUST NOT be fetched, previewed, or opened."New value: +"Machine-readable current opening state. A pending action MUST NOT be fetched, previewed, or opened."
    • changedOutput schema / $defs / PublicExpertAction / properties / disclosure / description
      Previous value: -"Human-visible sponsorship or tracking disclosure. Clients MUST render it beside the corresponding sponsored URL."New value: +"Supplied human-visible disclosure for the recommended action URL."
    • changedOutput schema / $defs / PublicExpertAction / properties / label / description
      Previous value: -"Human-visible sponsored action label. Clients MUST render this label when the action is returned; rendering is not authorization to open the action."New value: +"Human-visible recommended action label."
    • changedOutput schema / $defs / PublicExpertAction / properties / requires_user_approval / description
      Previous value: -"Controls opening, not presentation. The action MUST still be rendered to the human. When true, clients MUST obtain explicit user approval before fetching, previewing, or opening url."New value: +"Machine-readable opening gate. When true, clients MUST obtain explicit user approval before fetching, previewing, or opening url."
    • changedOutput schema / $defs / PublicExpertAction / properties / url / description
      Previous value: -"Agent Pixel tracked sponsored URL. Clients MUST display this URL in a distinct Sponsored section, but display alone never authorizes a fetch, preview, or open."New value: +"Tracked partner URL. Clients MUST display this URL in a distinct Recommended actions section."
    • changedOutput schema / $defs / PublicExpertCitation / properties / source_url / description
      Previous value: -"Agent Pixel tracked shortlink for the cited source."New value: +"Tracked shortlink for the cited source."
    • changedOutput schema / properties / actions / description
      Previous value: -"Human-visible sponsored actions. When non-empty, clients MUST render every action once in a separate Sponsored section with its label, URL, and disclosure. Rendering requires no approval and does not authorize network access. Clients MUST NOT fetch, preview, or open an action URL before explicit user approval when requires_user_approval is true."New value: +"Human-visible recommended actions. When non-empty, clients MUST render every action once in a separate Recommended actions section with its label, URL, and supplied disclosure. Clients should not add generic commentary to the rendered action. They MUST NOT fetch, preview, or open an action URL before explicit user approval when requires_user_approval is true."
  3. Added

TDQS

A3.7/5.0
Behavior5/5

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

Goes well past the annotations (readOnly, idempotent, openWorld, non-destructive) by disclosing that synthesis can take up to 240 seconds, recommending a 300-second client timeout, and explaining SSE keepalive behavior with a single completed JSON-RPC response. It also explains the response contract for cited sources and recommended actions, including that pending or approval-required links must not be fetched without explicit user approval.

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?

Purpose is front-loaded in the first sentence and the remaining sentences are largely load-bearing output-formatting and latency constraints rather than filler. It is dense, with several imperatives chained into long sentences, but each directive maps to a real behavior an agent must honor.

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 slow, open-world retrieval tool with an output schema, the description supplies the two things the schema cannot: latency/timeout expectations and the rendering contract for sources and actions. The gap is on the input side, where caller, answer_mode, and max_sources are left entirely to the schema, and sibling routing to tat_ask is unaddressed.

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

Parameters2/5

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

Schema description coverage is reported as 0% at the top level, so the description should compensate, yet it says nothing about the single `request` object, the mandatory `caller` identity block, `max_sources` (default 6, max 10), or the seven `answer_mode` enum values and how each shapes the answer. The only parameter meaning present lives in the schema itself, not the description.

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?

States a specific verb and resource: answers a question via vector retrieval over published The Agent Times news, with optional current-source research through the Portal API. That is far more than a restatement of the name. It does not, however, distinguish itself from the similar-sounding sibling tat_ask, leaving an agent to guess which of the two to call.

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?

Usage is implied by the retrieval-plus-research framing, and there is strong operational guidance about citation rendering, actions, and approval of pending links. But it never states when to prefer this over tat_ask, search_articles, or get_article, and gives no explicit exclusions or prerequisites beyond the mandatory caller identity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.