Skip to main content
Glama
bykarantelicom

bykaranteli-mcp

by bykarantelicom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

New and delisted perpetual contracts

get_new_listings
Read-only

Retrieve new perpetual listings and delistings across exchanges, showing which exchange listed a coin first; set a day window and choose compact or full detail.

Instructions

Call this when the user asks what new perpetuals were listed, which exchange listed a coin first, or about delistings. Returns listings and delistings across every exchange the hourly scan covers. Pass detail "compact" for a shorter page or "full" for the whole answer.

Input Schema

NameRequiredDescriptionDefault
daysNoWindow in days, 1-30 (default 30). Longer listing history is the listings dataset at bykaranteli.com/data.
detailNoOptional. "compact": a shorter page than the default (fewer rows, newest points kept, rounded figures, long text cut, grids left out; every cut named in trimmed). "full" or true: the whole route answer, still under the 100,000 character ceiling (the largest boards answer the ceiling note then: narrow them with symbol, limit or days instead). Omitted or false: the default first page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / detail
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "enum": [
+        "compact",
+        "full"
+      ],
+      "type": "string"
+    }
+  ],
+  "description": "Optional. \"compact\": a shorter page than the default (fewer rows, newest points kept, rounded figures, long text cut, grids left out; every cut named in trimmed). \"full\" or true: the whole route answer, still under the 100,000 character ceiling (the largest boards answer the ceiling note then: narrow them with symbol, limit or days instead). Omitted or false: the default first page."
+}
  2. Changed1 schema field changedv0.27.2
    • changedInput schema / properties / days / description
      Previous value: -"Window in days, 1-30 (default 30). Longer listing history is the paid x402 dataset."New value: +"Window in days, 1-30 (default 30). Longer listing history is the listings dataset at bykaranteli.com/data."
  3. Addedv0.9.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint, so safety is already covered; the description adds real context beyond that -- the data comes from an hourly scan and spans every covered exchange, and the detail flag trades page size against completeness. It stops short of describing ordering, freshness lag, or result shape in any detail.

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?

Three sentences: trigger first, coverage second, parameter guidance last. Every sentence carries distinct information and nothing is repeated from the annotations or the name.

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 no output schema, the description does the work of explaining what comes back (listings plus delistings across exchanges) and how 'detail' changes the payload. The one gap is the time-window dimension -- the 30-day default and the cut-off to the external dataset are left entirely to the schema.

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 coverage is 100%, so the baseline is 3. The description reinforces the 'detail' parameter's compact/full tradeoff in plain language, which is mild added value, but it says nothing about the 'days' window -- the 1-30 day constraint and the pointer to the external listings dataset live only in the schema.

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 names a specific resource (new and delisted perpetual contracts) and a specific scope (across every exchange the hourly scan covers), which no sibling tool covers -- get_jupiter_perps and get_solana_perps are venue-specific market views, not listing/delisting feeds. The opening line maps directly to user question phrasing, so the tool's role is unambiguous.

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?

It gives explicit user-question triggers ('what new perpetuals were listed', 'which exchange listed a coin first', 'about delistings') that tell an agent exactly when to reach for it. It does not name an alternative tool or state when NOT to use it, which keeps it short of a 5.

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