> ## Documentation Index
> Fetch the complete documentation index at: https://docs.meridiandata.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Tool ID and methods

> Pin Meridian directly in Context Protocol using its stable marketplace identifier.

## Meridian marketplace tool ID

```text theme={null}
e5e62fa5-28e1-42f4-8b84-f4866234df43
```

Use this UUID in Context SDK `tools` or `toolId` fields and in the official MCP server's `toolIds` or `toolId` fields.

## Methods

| Method                | Purpose                                                                          |
| --------------------- | -------------------------------------------------------------------------------- |
| `futures`             | Normalized futures OHLCV, trade flow, OI, funding, premium, and liquidation data |
| `spot`                | Normalized spot OHLCV and buy/sell trade-flow data                               |
| `custom_bars_catalog` | Discover stored custom-bar types, thresholds, source runs, and ranges            |
| `custom_bars`         | Query stored dollar, volume, tick, and imbalance bars                            |

## Verify the listing

Marketplace metadata can change when methods are refreshed. Applications that depend on Execute mode should verify the listing at startup or deployment time:

<CodeGroup>
  ```typescript TypeScript theme={null}
  const tool = await client.discovery.get(
    "e5e62fa5-28e1-42f4-8b84-f4866234df43"
  );

  console.log(tool.name);
  console.log(tool.mcpTools);
  ```

  ```python Python theme={null}
  tool = await client.discovery.get(
      "e5e62fa5-28e1-42f4-8b84-f4866234df43"
  )

  print(tool.name)
  print(tool.mcp_tools)
  ```
</CodeGroup>

<Warning>
  Do not substitute a display name for the UUID. Display names are for people; the tool ID is the stable integration identifier.
</Warning>