Skip to main content
Glama
Sign In
Molpha MCP

Molpha MCP

Official
by molpha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Derive Molpha feedId

molpha_derive_feed

Compute the feedId for an oracle spec locally from API config and signature requirements, with no transaction needed. Use it to preview feedId before fetching verified data or settling.

Instructions

Locally derive the feedId for a declarative spec (apiConfig + quorum) — no transaction, no subscription required. feedId = keccak256(owner || apiConfigHash || signaturesRequired); the feed itself is created lazily on-chain at first settle (subscription or x402 round). Call this to preview a feedId before molpha_fetch_verified, or to check what feedId a given spec resolves to for the current signer. Prefer settled/finalized data — independent nodes must converge on a byte-identical value to co-sign.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "apiConfig": "<apiConfig>",
      "signaturesRequired": "<signaturesRequired>"
    },
    "name": "molpha_derive_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiConfigYes
signaturesRequiredYes
rejectNonDeterministicNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so thoroughly. It discloses that computation is local, requires no transaction or subscription, that the feed is created lazily on-chain at first settle, and that independent nodes must converge on a byte-identical value, which implies a deterministic algorithm. This is a rich behavioral disclosure beyond simple read/write hints.

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 compact and information-dense, covering purpose, formula, use cases, and determinism requirements in just a few sentences. Every sentence adds value and there is no redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description provides strong context for the main computation and use, but it omits the return value format, which is critical since there is no output schema. It also does not cover edge cases like invalid specs or how rejectNonDeterministic affects behavior. Given the nested apiConfig complexity and absence of an output schema, the description is incomplete for full agent comprehension.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain the parameters. It explains apiConfig and signaturesRequired via the formula 'feedId = keccak256(owner || apiConfigHash || signaturesRequired)', but the third parameter, rejectNonDeterministic, is never mentioned. It also does not explain the structure or required fields within apiConfig, leaving the agent to infer from the bare schema. This incomplete compensation for a low-coverage schema warrants a low score.

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 the tool's function: 'Locally derive the feedId for a declarative spec (apiConfig + quorum)'. It uses a specific verb ('derive') and resource ('feedId'), and distinguishes itself from siblings by emphasizing local derivation and the fact no transaction/subscription is required, contrasting with molpha_fetch_verified.

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

Usage Guidelines5/5

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

The description explicitly tells when to use the tool: 'Call this to preview a feedId before molpha_fetch_verified, or to check what feedId a given spec resolves to for the current signer.' It also advises preferring settled/finalized data, giving important context about when relying on this derived value is appropriate vs. using verified data.

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