Skip to main content
Glama

AINDEX

What happened to an agent

get_agent_feed
Read-only

What happened to an agent since a time, oldest first: wake conditions that fired, trades, stops and steps that need the owner. Poll it, or set a webhook with update_agent and read it when pinged. Pass the latest it returned as after next time.

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": {
      "agent": "<agent>"
    },
    "name": "get_agent_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoUnix seconds; omitted: the last 24 hours.
agentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds value beyond that with ordering ('oldest first'), the item taxonomy returned, and the pagination cursor idiom. It does not state rate limits or what an empty feed looks like, keeping it below a 5.

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?

Three short sentences, front-loaded with what the feed is and what it returns, followed by usage and cursor mechanics. Every clause carries information; nothing is redundant with the name or title.

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 read-only, two-parameter polling tool with no output schema, the description substitutes well by enumerating the returned item kinds. What is missing is any indication of the shape/fields of those items or volume expectations, though this is a minor gap given the annotations already settle the safety profile.

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 50%: `after` is documented in the schema (Unix seconds, default last 24 hours), and the description reinforces it with real cursor semantics — 'Pass the latest it returned as after next time' — which is genuine added meaning. However, the `agent` parameter is undocumented in both the schema and the description beyond the regex pattern, so the description only partially compensates for the gap.

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 names a specific resource (an agent's feed) and enumerates exactly what it contains — wake conditions that fired, trades, stops, and steps needing the owner — plus the ordering ('oldest first'). An agent can distinguish this from siblings like update_agent or agent_check_step without opening any schema.

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?

It gives concrete operating guidance: 'Poll it, or set a webhook with update_agent and read it when pinged,' which names a real alternative (update_agent) and the condition under which each applies. It lacks explicit when-not-to-use guidance, but the polling-vs-webhook split covers the main decision an agent faces.

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.

Resources