Skip to main content
Glama

swiss-living-index

Data freshness

data_freshness
Read-onlyIdempotent

How current the Swiss Living Index data is: every scheduled official data source with where it runs (cloud, a Mac on the Swiss network, or the A5000 language-model machine), its cadence in days, the last successful check, the next due date and a status (current, due, overdue = more than twice its cadence, new = not run yet), plus a summary. Use it to state how fresh a figure is before relying on it. Optional status filter.

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

Input Schema

NameRequiredDescriptionDefault
statusNooptional filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, yet the description still adds substantial content: where each source runs, cadence in days, what counts as 'overdue' (more than twice its cadence) and 'new' (not run yet). Those operational definitions are exactly the kind of context annotations cannot express.

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?

Purpose and the use case are front-loaded in separate sentences with no filler. The first sentence is dense and enumerates many returned fields, but every element listed is material to interpreting the report; only the status enumeration overlaps with the schema.

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

Completeness5/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 carries the full burden and discharges it by enumerating the returned fields, the status vocabulary and its thresholds, and the presence of a summary. Nothing an agent needs to interpret or invoke this read-only report is missing.

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?

Schema coverage is 100% and the single parameter is a four-value enum, so the baseline is 3. The description goes beyond the schema by defining what each status value means (current, due, overdue = >2x cadence, new = not run yet), which helps the agent predict filter results rather than just pick a string.

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?

States precisely what is reported: per-source freshness metadata (location, cadence, last successful check, next due date, status) plus a summary. An agent immediately knows this is a data-provenance/freshness report rather than a data lookup like its siblings. It does not name a differentiated sibling such as list_datasets or get_dataset, so it stops short of a 5.

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?

Gives an explicit usage condition: 'Use it to state how fresh a figure is before relying on it.' That is a concrete when-to-use tied to citing statistics. It offers no when-not guidance and names no alternative tool, so it is clear context without exclusions.

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