Pay-per-call DRT/ICT crypto trading signals for AI agents (LONG/SHORT, entry/SL/TP).
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Average 3.6/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clearly described and unambiguous.
With a single tool, naming consistency is trivially maintained. The name 'get_signals' follows a standard verb_noun pattern and is descriptive.
A single tool feels very thin for a server dedicated to trading signals. While the specific API might only expose one endpoint, this severely limits the server's utility and suggests a very narrow scope.
The server only fetches signals. There are no supporting tools for managing signal preferences, retrieving historical signals, or acting on signals (e.g., placing orders), which are natural extensions for a trading-oriented server. This leaves significant gaps in the expected workflow.
get_signalsAInspectFetches DRT/ICT crypto trading signals (LONG/SHORT with entry, SL, TP, R:R) from the Northcap x402 pay-per-call API. Optionally filter by symbol and limit.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of signals to return (max 50) | |
| symbol | No | Symbol filter, e.g. BTCUSDT, ETHUSDT |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full transparency burden. It discloses the pay-per-call nature (a cost implication) and indicates a fetch operation (implying read-only), but it does not explicitly state side effects, rate limits, or error behavior. The cost disclosure is a positive trait, but additional details like idempotency or return format absent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that leads with the core purpose, then details the signal content and optional filters. Every word adds value, with no redundancy or fluff. It is excellently front-loaded and concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no output schema and only two optional parameters, the description provides essential context: what the tool returns (trading signals with specific fields), the data source, and available filters. It lacks explicit mention of return format (e.g., array of objects) or error handling, but for a simple fetch tool, it covers the key aspects sufficiently. Slight deduction for not describing the response structure.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already provides 100% coverage for both parameters (limit with min/max, symbol with example). The description only repeats 'Optionally filter by symbol and limit' without adding extra meaning, such as how the limit interplays with pagination or symbol format constraints. Baseline of 3 is appropriate given the schema's thoroughness.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Fetches' and the resource ('DRT/ICT crypto trading signals') while specifying the signal content (LONG/SHORT with entry, SL, TP, R:R). It also names the source API (Northcap x402) and notes optional filtering, making its purpose unambiguous even without sibling tools to differentiate.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance is provided on when to use this tool versus alternatives. The mention of 'pay-per-call' implies a cost consideration but does not offer direct advice on appropriate usage contexts or exclusions. There are no sibling tools listed, but the description still lacks explicit when-to-use or when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!