Skip to main content
Glama

Reality lag map: how fresh every Orb Studio sensor is

get_freshness
Read-only

Free. For every Orb Studio sensor: the time the source's data refers to, its age in hours, the age that is normal for that source (update interval plus usual publication delay) and a status: on_time, late, stale, unknown (the source does not say when it measured), no_data, or event (event feeds and manual input). Read numbers together with their age: a live price, a daily gas day and a yearly crime statistic describe different moments. Timeliness only, not accuracy.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the cost ('Free'), the fact that it covers all sensors with no filtering, and the full status vocabulary, including the non-obvious meaning of 'unknown' (the source does not say when it measured) and 'event' (event feeds and manual input). That is meaningful behavior beyond the annotations, though it says nothing about result size or ordering when every sensor is returned.

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?

It is dense but every clause carries information: the scope, the returned fields, the status vocabulary, and the caution about comparing ages. The leading 'Free.' is slightly abrupt and the middle sentence is long, but nothing is filler.

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 parameters and no output schema, the description has to carry the return shape itself, and it does: it enumerates the fields and all status values. Nothing an agent needs in order to call this correctly or interpret the response 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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. The description correctly implies an unfiltered sweep of all sensors rather than a per-sensor lookup.

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 states the resource ('every Orb Studio sensor') and exactly what is returned for each: reference time, age in hours, normal age, and a status. The closing line 'Timeliness only, not accuracy' draws a clean boundary between this tool and the sibling sensor-data tools, so an agent can tell what this is for without opening anything else.

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 real interpretive guidance ('Read numbers together with their age: a live price, a daily gas day and a yearly crime statistic describe different moments') and implicitly routes value-fetching elsewhere via 'Timeliness only, not accuracy.' It stops short of naming an alternative tool or stating when not to call it, so it is clear context rather than full routing.

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.