stillos-edge-gate
Server Details
Grade a track record before risking capital: REAL_EDGE/REGIME_LUCK/NEGATIVE_EV. Fail-closed.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- stillmarcus24/stillos-edge-gate
- GitHub Stars
- 0
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.
Tool Definition Quality
Average 4.2/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined and unambiguous.
A single tool cannot exhibit inconsistency. The name 'grade_strategy' follows a clear verb_noun pattern, which is consistent with best practices.
One tool is borderline for a server focused on strategy grading. While the tool itself is well-scoped, additional tools for context (e.g., fetching strategy parameters or comparing results) might be expected, but the narrow focus is acceptable.
The tool covers the core function of grading strategies comprehensively (holdout, adjustments, significance test). However, missing auxiliary operations like listing past grades or retrieving receipts could be minor gaps for an agent.
Available Tools
1 toolgrade_strategyAInspect
Grade a trading/strategy track record BEFORE committing capital. Returns one verdict -- REAL_EDGE, REGIME_LUCK, NEGATIVE_EV, or INSUFFICIENT_DATA -- via chronological out-of-sample holdout, fee+slippage adjustment, and a significance test. Fail-closed. Includes a signed, independently verifiable receipt when reachable.
| Name | Required | Description | Default |
|---|---|---|---|
| agent | No | who is asking (for the receipt) | |
| trades | Yes | settled trades |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden. It discloses the tool is 'Fail-closed', includes a 'signed, independently verifiable receipt', and outlines the methodology (chronological holdout, fee+slippage adjustment, significance test). These are valuable behavioral traits beyond simple read-only.
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 three sentences with zero waste. The primary action and key output are front-loaded, and every sentence adds value (purpose, methodology, safety/receipt).
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?
Given 2 parameters, no output schema, and no siblings, the description covers purpose, timing, methodology, the four possible verdicts, and the receipt behavior. It is sufficient for an agent to understand what the tool does and what it returns, though it could briefly explain the verdict meanings.
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?
Schema coverage is 100%, so baseline is 3. The description adds minimal parameter detail beyond the schema; it mentions 'trades' and 'agent' but does not elaborate on their format or impact on the verdict. The schema already describes 'trades' as 'settled trades' and 'agent' as 'who is asking'.
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 uses a specific verb ('Grade') and resource ('trading/strategy track record'), and clearly states the action to be performed before committing capital. It distinguishes the tool's purpose without sibling comparison needed.
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?
The description explicitly says 'BEFORE committing capital', providing clear context for when to use. It also mentions 'Fail-closed' as a safety property. However, it does not provide explicit when-not-to-use guidance or alternatives, though no siblings exist to contrast.
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.
Discussions
No comments yet. Be the first to start the discussion!