Skip to main content
Glama

Agent News by The Agent Times

Recommend Agent Tools

tat_recommend
Read-onlyIdempotent

Return a sourced recommendation synchronously using published TAT news, lexical fallback when embeddings are unavailable, and Portal synthesis. Preserves TAT answer-standard and citation checks. Returns answered, insufficient_evidence, or service_unavailable; no background processing ticket. Allow a 300-second client timeout. Not an external-resource safety checker.

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": {
      "use_case": "<use_case>"
    },
    "name": "tat_recommend"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idNoOptional 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.
use_caseYesAgent/operator use case
constraintsNoOptional constraints
source_agentNoCalling agent identifier

Output Schema

NameRequiredDescriptionDefault
textNoPresent when the tool returns a text-only response.
agent_idYesPersistent 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_identityYesPersistence instructions and the next step for reusing agent_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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."
  2. 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"
      +]
  3. Changed1 schema field changed
    • removedInput schema / properties / allow_external_search
      Removed value: -{
      -  "description": "Allow OpenRouter-backed external search (default true)",
      -  "type": "boolean"
      -}
  4. First observed

TDQS

A3.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses real operational traits: synchronous execution, a lexical fallback when embeddings are unavailable, preserved answer-standard and citation checks, three named return statuses, absence of a background ticket, and a concrete 300-second client timeout expectation. These are exactly the latency and failure-mode details an agent needs before calling.

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?

Four dense sentences, front-loaded with the core action and mechanism, with no filler. The trailing 'Not an external-resource safety checker' is the one line whose placement is unclear and could be integrated more usefully.

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?

With an output schema and rich annotations already present, the description supplies the remaining behavior an agent needs (statuses, timeout, citation checks). The only meaningful gap is the lack of sibling differentiation for choosing this over other ask/recommend tools.

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 coverage is 100% and each parameter carries its own description, so the schema already does the heavy lifting. The prose mentions no parameter behavior or format detail beyond what the input schema states, so the baseline 3 applies.

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?

The description gives a specific verb and output ('Return a sourced recommendation') and names its data sources (published TAT news, lexical fallback, Portal synthesis). It does not differentiate itself from closely related siblings like tat_ask or ask_expert, and the title 'Recommend Agent Tools' is slightly at odds with a recommendation engine over news content, which could confuse an agent.

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?

There is no explicit statement of when to use this versus tat_ask, ask_expert, or tat_search. The only scoping cue is the negative 'Not an external-resource safety checker,' which excludes a category without routing the agent to an alternative, leaving selection largely to inference.

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.