Skip to main content
Glama

Get Market Freshness Index

get_market_freshness_index
Read-only

Get live real-time price freshness metrics across OunceScout catalog: counts of verified listings under 4 hours, stale items, continuous verification cycle metrics, and IndexNow broadcast status.

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_market_freshness_index"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered by structured fields. The description adds meaningful return-content context (verified-under-4-hours counts, stale items, verification cycle metrics, IndexNow broadcast status) that is not in annotations, but it says nothing about data latency, caching, or whether the broadcast status is read-only observation versus triggering.

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?

A single front-loaded sentence with a colon-delimited list of metrics, which is efficient and scannable. Minor waste from the redundant 'live real-time' phrasing, but no sentence lacks purpose.

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, read-only metrics tool with no output schema, the description covers the main categories of returned data well enough to call it correctly. It stops short of describing the response shape or units, which would matter more if the metrics were consumed programmatically.

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 semantics burden and the baseline of 4 applies. The description correctly describes no inputs and instead spends its words on scope, which is the right allocation for a zero-arg tool.

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 uses a specific verb plus resource ('Get live real-time price freshness metrics across OunceScout catalog') and enumerates the exact metrics covered, so an agent knows precisely what this returns. It does not, however, explicitly contrast itself with lookalike siblings such as get_premium_index or get_live_spot_prices, leaving ambiguity about which 'index' tool to pick.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use statement, no mention of alternatives, and no prerequisites. The catalog-freshness framing only implicitly suggests a monitoring use case; an agent has to infer whether this is for debugging ingestion, checking staleness before a quote, or general health checks.

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