Skip to main content
Glama

ADS Beast

client_data_freshness

Read-only

When each client and platform was last synced. Call it before a deep analysis so stale data is named as stale.

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

Input Schema

NameRequiredDescriptionDefault
client_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered; the description's useful addition is the guidance to run it pre-analysis to flag staleness. It does not disclose staleness thresholds, how missing/never-synced platforms are reported, or response granularity, which are the traits an agent would still need.

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?

Two short sentences, zero filler, and the subject matter is front-loaded ahead of the usage instruction. Nothing in it could be cut without losing information.

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 no output schema, the description does carry the burden of describing returns and it does so at a high level ('when each client and platform was last synced'); annotations cover the read-only safety profile. The remaining hole is the client_id scoping behavior, which leaves the definition slightly short for correct invocation.

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 the single client_id parameter, and the description never mentions whether it is an optional filter, what the default (all clients) behavior is, or which client scope a call covers. 'Each client and platform' only weakly implies unfiltered multi-client output, so the schema gap is largely uncompensated.

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 states exactly what the tool surfaces: last-synced timestamps broken out per client and platform. That verb-plus-resource framing lets an agent distinguish it from analytics/report siblings without opening the schema, though it never states the operation's name or return shape explicitly.

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 a concrete trigger — call it before a deep analysis so stale data is named as stale — which is a clear usage condition rather than a vague hint. It stops short of naming alternatives or saying when freshness checks are unnecessary, so it is strong context but not full when/when-not guidance.

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.