Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opensea_collection_chart

Track an OpenSea collection's floor price or traded volume over time, returning a series with each sample in both the settlement token and USD.

Instructions

Get an OpenSea collection's price or volume history. Returns a time series for a collection — either its floor price or its traded volume — over the requested window, with each sample in both the settlement token and USD. Use metric=floor_price for the floor line and metric=volume for the volume bars.

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": {
      "slug": "<slug>"
    },
    "name": "opensea_collection_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesOpenSea collection slug
metricNoSeries to return
timeframeNoWindow

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / metric / enum
      Added value: +[
+  "floor_price",
+  "volume"
+]
    • addedInput schema / properties / timeframe / enum
      Added value: +[
+  "ONE_HOUR",
+  "ONE_DAY",
+  "SEVEN_DAYS",
+  "THIRTY_DAYS",
+  "ALL_TIME"
+]
  2. Addedv1.16.2

TDQS

A4.4/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 burden of behavioral disclosure. It explains that the tool returns a time series, that each sample is in both the settlement token and USD, and that metric selects floor price vs volume. It does not mention rate limits or pagination, but the core read-only behavior and output shape are clear.

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 two sentences with no filler. The main action and resource are front-loaded, followed by the return format and metric usage guidance. Every sentence contributes useful information.

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?

For a simple three-parameter tool with complete schema coverage and no output schema, the description provides the missing return context: a time series, the two possible metrics, and dual-currency samples. It does not detail granularity or error behavior, but it is sufficient for correct selection and invocation.

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?

The schema already documents all three parameters with 100% coverage, giving a baseline of 3. The description adds meaningful semantics beyond the schema by mapping metric=floor_price to the floor line and metric=volume to volume bars, and by clarifying that timeframe is the requested window.

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 states a specific action and resource: getting an OpenSea collection's price or volume history as a time series. It clearly distinguishes this from other OpenSea collection tools by emphasizing floor price and traded volume over a window.

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: when a collection's floor-price or volume history is needed. It also provides metric-specific guidance ('Use metric=floor_price for the floor line and metric=volume for the volume bars'), though it does not explicitly name alternatives among the OpenSea sibling tools.

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