Skip to main content
Glama
HorizenOfficial

horizen-mcp

Official
by HorizenOfficial
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

fetch_stork_price

Fetch a live signed price update from the Stork REST API using your STORK_API_KEY. Returns Solidity-annotated payload with solidityCallData ready for updateTemporalNumericValueV1.

Instructions

Perform an authenticated pull from the Stork REST API to get a live signed price update for an asset. Reads the Stork API key from the STORK_API_KEY environment variable (not a tool argument). Returns the full signed payload with each field annotated with its correct Solidity type (timestampNs as uint64 in nanoseconds; quantizedValue as int192 — not uint256). Use the solidityCallData field directly when constructing an updateTemporalNumericValueV1 call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetIdYes
baseUrlNoStork REST API base URL. Must be a stork-oracle.network host. Defaults to https://rest.jp.stork-oracle.network. The API key is read from the STORK_API_KEY environment variable, not passed as an argument.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / apiKey
      Removed value: -{
-  "minLength": 1,
-  "type": "string"
-}
    • changedInput schema / properties / baseUrl / description
      Previous value: -"Stork REST API base URL. Defaults to https://rest.jp.stork-oracle.network"New value: +"Stork REST API base URL. Must be a stork-oracle.network host. Defaults to https://rest.jp.stork-oracle.network. The API key is read from the STORK_API_KEY environment variable, not passed as an argument."
    • changedInput schema / required
      Previous value: -[
-  "assetId",
-  "apiKey"
-]New value: +[
+  "assetId"
+]
  2. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states that authentication is required, reads the API key from the STORK_API_KEY environment variable rather than a tool argument, and documents non-obvious return-type details like timestampNs as uint64 and quantizedValue as int192, not uint256. It does not cover failure modes or rate limits, but the core behavioral traits are disclosed.

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 concise and front-loaded with the core action, then delivers key behavioral details and return-type corrections in four tight sentences. Every sentence adds value, and the critical int192 warning is clearly highlighted.

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?

Given the lack of an output schema, the description appropriately explains the return payload's key fields and the correct Solidity types, plus how to use solidityCallData. It is sufficient for safely invoking the tool and consuming its primary output, though it does not enumerate all possible response fields or error conditions. Overall, the essential context is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents baseUrl well, and assetId has only a pattern. The description ties assetId to 'an asset' and explains that the API key is environment-based, but it does not expand on assetId format or provide examples. At 50% schema description coverage, the description adds some meaning but does not fully compensate for the gap.

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 starts with a specific verb and resource: 'Perform an authenticated pull from the Stork REST API to get a live signed price update for an asset.' This clearly defines the tool's function and distinguishes it from the sibling info/contract/token tools, which serve different purposes.

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?

The description gives clear context for when to use the tool: whenever a live signed price update for an asset is needed. It also provides follow-on guidance for constructing an updateTemporalNumericValueV1 call with the returned solidityCallData. It does not explicitly name alternatives or exclusions, but none of the sibling tools appear to provide this price-fetching functionality.

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

Deploy Server

Other Tools