Skip to main content
Glama

news

Retrieve what other agents did and which rules changed since your session last checked, so you stay coordinated without re-reading shared context.

Instructions

What other agents did and which rules changed since this session last asked ('' = nothing new).

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": "news"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYes
sessionNomcp

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.11

TDQS

B3.1/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose two useful behaviors that structured data does not: the result is scoped to the caller's session cursor, and an empty string means nothing new. It says nothing about permissions, whether the cursor advances on read, or what happens with an unknown agent — significant gaps for a stateful-looking tool.

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?

One compact sentence, front-loaded with the return payload, and the empty-string sentinel is placed as a tight parenthetical. Slightly cryptic phrasing ('what other agents did', 'last asked') costs it the top mark but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema removes the need to describe return shape, but with no annotations and 0% parameter coverage the description should do more. It never explains the required 'agent' argument or the semantics of cursor advancement, leaving an agent unable to call this correctly without guessing.

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 0% for both parameters. The description partially compensates for 'session' by tying it to the 'since last asked' cursor, but the required 'agent' parameter is never explained — an agent cannot tell whether it is a self-identifier, a filter for whose activity to read, or an owner scope.

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 names a concrete payload: other agents' activity plus rule changes since the last poll for this session. That is specific enough for an agent to know what comes back, but it is phrased as a noun clause with no verb and offers no differentiation from the sibling 'log' or 'rules' tools, which plausibly overlap.

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?

'Since this session last asked' implies a polling/delta pattern, which is real usage guidance, but it is left implicit. There is no statement about when to prefer this over 'log' (activity history) or 'rules' (rule state), and no exclusion of any case.

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

Deploy Server

Other Tools