Skip to main content
Glama
noblabs

lit-forge MCP server

マーケット温度計(リスクオン/オフ合成スコア)

get_market_thermometer

Synthesizes VIX, S&P 500, US 10Y yield, and dollar index changes into a 0-100 risk-on/off score. Provides component scores and 30-day trend for market overview.

Instructions

VIX・S&P 500 前日比・米10年金利前日比・ドル指数前日比を合成した 0-100 のリスクオン/オフ・スコアを返します。50 が中立、70 以上でリスクオン優勢、30 以下でリスクオフ優勢。各成分のスコアと過去 30 営業日の推移も含みます。投資推奨ではなく俯瞰用の指標です。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description carries the burden of behavioral disclosure. It explains the score interpretation (50 neutral, 70+ risk-on, 30- risk-off) and disclaims it as non-investment advice. It might benefit from noting it is a read-only operation, but overall transparent.

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?

The description is a single, well-structured sentence that covers components, thresholds, extra details (30-day history), and a disclaimer. It is concise and front-loaded with the main function.

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?

Given no parameters and no output schema, the description fully covers what the tool returns: a composite score, component scores, and historical data. It also includes a necessary disclaimer. No gaps remain.

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?

There are no parameters (100% coverage in schema), so the baseline is 4. The description adds no parameter semantics but enriches understanding of the tool's output, which is acceptable given no parameters.

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 clearly states it returns a composite risk-on/off score (0-100) synthesizing VIX, S&P 500, 10-year yield, and dollar index. It distinguishes itself from siblings that provide raw quotes or snapshots by offering a synthesized indicator.

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

Usage Guidelines3/5

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

The description does not explicitly specify when to use this tool versus alternatives like get_market_snapshot or get_quote. It implicitly suggests use as an overview indicator but lacks direct comparisons or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/noblabs/lit-forge-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server