Skip to main content
Glama

TickDB Market Data

by io.github.TickDB
OverviewDiscussionsAdmin

get_api_key_subscriptions

Query API key subscriptions and expiration information without website login.

    Uses the current request's X-TickDB-Key or the server's TICKDB_API_KEY;
    no tool arguments are required. Preserves the upstream response envelope.
    Data includes user_id, server_time, total and api_keys. Key records include
    id, key_prefix, name, plan, status, expires_at, remaining_seconds and
    created_at. Use server_time and remaining_seconds to assess expiration;
    preserve missing/null values rather than treating them as zero.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the auth source, that the upstream response envelope is preserved, the exact returned fields, and the rule to preserve nulls rather than coerce to zero. It stops short of error behavior or rate limits, but the read-only nature is clear from 'Query'.

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?

Purpose is front-loaded in the first clause, followed by operational details. The enumerated field list is longer than typical but earns its place because no output schema exists to document the return shape elsewhere.

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

Completeness5/5

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

For a no-arg, no-output-schema read tool, the description covers everything needed to call it correctly: credential sourcing, absence of arguments, the returned field set, and how to interpret expiration via server_time/remaining_seconds. Nothing essential for correct invocation is missing.

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 tool takes zero parameters, so the baseline is 4. The description reinforces that no arguments are required and that the credential comes from the request/server environment rather than a parameter.

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 verb and resource ('Query API key subscriptions and expiration information') and is instantly distinguishable from all siblings, which are market-data tools. It also clarifies the auth context (X-TickDB-Key / TICKDB_API_KEY) so the agent knows which credential scope applies.

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 establishes clear context for invocation: no website login is needed, no arguments are required, and the current request key is used automatically. It does not name when-not or alternative tools, but no sibling overlaps this capability, so the missing exclusion costs little.

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

All TickDB Market Data 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