Skip to main content
Glama
Sign In

DalalOS: Indian Stock Market Research (NSE/BSE)

by in.dalalos
OverviewDiscussionsAdmin

Data freshness

get_data_freshness
Read-onlyIdempotent

Use this when the user asks how recent DalalOS data is, or when a figure looks stale.

Report cache freshness: last successful refresh per data domain and overall health.

Every scraper-backed domain (including fii_dii and the ipos family) carries a staleness
threshold matched to its real refresh cadence, so a domain whose scraper job silently stops
running gets flagged stale rather than reporting `max_age_hours: null` forever.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "additionalProperties": true,
-      "title": "Result",
-      "type": "object"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_data_freshnessOutput",
-  "type": "object"
-}New value: +null
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "additionalProperties": true,
+      "title": "Result",
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_data_freshnessOutput",
+  "type": "object"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world. The description adds genuinely new context: results are per-domain, include an overall health signal, and staleness thresholds are matched to each domain's real refresh cadence so a silently stopped scraper surfaces as stale instead of a perpetual null. Since there is no output schema, this return-shape information is doing necessary work; only the exact field names/format are left implicit.

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?

Front-loads the trigger and the payload in two short sentences. The third sentence on staleness thresholds is longer than needed but earns its place by explaining a non-obvious behavior (null max_age_hours vs. flagged stale).

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 parameters and no output schema, the description must convey what comes back; it names the two return components (per-domain last refresh, overall health) and the staleness semantics. An agent could call it correctly. Exact response keys and domain enumeration remain unspecified, which keeps it short of a 5.

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?

Zero parameters, so the baseline is 4. The description correctly implies a call with no arguments and no scoping options, leaving nothing ambiguous.

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 and resource: 'Report cache freshness: last successful refresh per data domain and overall health.' No sibling tool covers this diagnostic/meta concern (the others fetch market or company data), so it is unambiguously distinguishable.

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?

Opens with an explicit trigger: 'Use this when the user asks how recent DalalOS data is, or when a figure looks stale.' That covers the main invocation contexts. It does not enumerate when not to use it, but no sibling competes for the same job, so the omission is minor.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All DalalOS: Indian Stock Market Research (NSE/BSE) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources