Skip to main content
Glama

collect_now

Refreshes all AI news sources on demand and reports how many new items each source added, including any failed sources and reasons.

Instructions

Collect new Items from every Source now.

    Use only when the user asks to refresh or collect now: `whats_new` already
    collects by itself when the data is over 24 hours old. Takes about a minute.
    Reports how many Items each Source added (0 for a failed one), and which Sources
    failed and why.
    

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "collect_now"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
failedYes
sourcesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and non-idempotent, open-world behavior, so the mutation profile is already covered. The description adds genuine context beyond that: expected duration (~1 minute) and the reporting contract, including that a failed Source reports 0 and that failure reasons are returned. It does not say whether concurrent invocations are safe or what happens to previously collected items, which keeps it short of 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?

Front-loads the core action in one sentence, then adds the gating condition, the cost estimate, and the return summary in that order. Every sentence carries information an agent needs to decide whether to call and what to expect; no filler.

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 zero-parameter, network-spanning collection tool, it covers purpose, gating condition, latency, and result shape, and an output schema exists so return values need no further explanation. Minor omissions (concurrency behavior, whether it is safe to interrupt) leave a small gap.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter meaning to establish beyond what the empty schema already conveys. Baseline 4 applies; the description correctly spends no words on inputs.

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?

States a specific verb (collect), resource (new Items), and full scope (from every Source), plus the immediacy ('now'). It also names the sibling `whats_new` and explains how they differ, so an agent can tell the two apart without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use trigger ("only when the user asks to refresh or collect now") and an explicit when-not-to-use rationale (`whats_new` already collects when data is over 24 hours old). The alternative is named and the condition that selects it is stated.

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