Skip to main content
Glama
Sign In

Solana MCP by Vybe

by io.github.vybenetwork
OverviewDiscussionsAdmin

Holder Count History

get-token-holder-count-history
Read-onlyIdempotent

Holder Count History. Calls only GET /v4/tokens/{mintAddress}/holders-count-ts and returns that response. Pass startTime and endTime as unix seconds. endTime minus startTime must be at most 2592000 seconds (30 days). interval is hour or day.

Input Schema

NameRequiredDescriptionDefault
pageNoPage selection, 0-indexed.
limitNoResult page size specifier.
endTimeYesEnd of the window as a unix timestamp in seconds. Required with startTime, and at most 30 days (2592000 seconds) later.
intervalNoTime bucket: hour or day. The startTime to endTime window must still be at most 30 days.
startTimeYesStart of the window as a unix timestamp in seconds. Required with endTime. endTime minus startTime must be at most 2592000 seconds (30 days).
mintAddressYesTyped Solana public key identifier used across request parameters and response fields. Path parameter for /v4/tokens/{mintAddress}/holders-count-ts.

Output Schema

NameRequiredDescriptionDefault
bodyNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / endTime / description
      Previous value: -"End time of period of interest as a unix timestamp."New value: +"End of the window as a unix timestamp in seconds. Required with startTime, and at most 30 days (2592000 seconds) later."
    • changedInput schema / properties / interval / description
      Previous value: -"Enumerates the supported time intervals for token holders."New value: +"Time bucket: hour or day. The startTime to endTime window must still be at most 30 days."
    • changedInput schema / properties / startTime / description
      Previous value: -"Start time of period of interest as a unix timestamp."New value: +"Start of the window as a unix timestamp in seconds. Required with endTime. endTime minus startTime must be at most 2592000 seconds (30 days)."
    • changedInput schema / required
      Previous value: -[
-  "mintAddress"
-]New value: +[
+  "mintAddress",
+  "startTime",
+  "endTime"
+]
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior. The description adds the exact endpoint and time-window limit, but it does not disclose pagination behavior despite page/limit parameters, nor rate limits or other operational context.

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?

The description is short and front-loads the endpoint and key constraints. The opening 'Holder Count History' repeats the title and earns little, but the rest is efficient.

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 a full output schema, high schema coverage, and safety annotations, the description provides enough context to call the tool. Pagination semantics for page/limit are the main unaddressed behavioral detail.

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?

Schema description coverage is 100%, so the schema already documents all parameters including unix timestamps, the 30-day window, and interval values. The description largely repeats those constraints rather than adding new parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the specific resource (holder count history) and exact endpoint, making the operation clear. It does not explicitly differentiate from related sibling tools such as get-token-top-holders, but the endpoint name supplies enough specificity.

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?

It tells the agent to pass startTime and endTime and gives the 30-day maximum constraint, which implies usage for historical holder-count time series. However, it does not state when to use this tool versus alternatives like get-token-top-holders or other token history tools.

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

All Solana MCP by Vybe 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