fde-agent
Server Details
Diagnose AI workflows for failure, security, and handoff risks — RED/AMBER/GREEN per node.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
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 single tool's purpose is clearly defined.
The single tool name 'diagnose_workflow' follows a clear verb_noun pattern. Consistency is not an issue with only one tool.
Having only one tool for a workflow diagnostic server is too thin. The server likely needs additional tools for configuration, result management, or comparison to be useful.
The server provides only a single diagnostic operation. Missing tools for listing previous diagnoses, managing workflow definitions, or comparing results, leaving significant gaps for typical workflows.
Available Tools
1 tooldiagnose_workflowDiagnose an AI workflow for failure / security / handoff risksAInspect
FDE Agent pre-mortem: analyze an agentic AI workflow and return per-node RED/AMBER/GREEN risk across failure, security, and handoff axes, grounded in an incident ontology. Provide a built-in sample ('legal' or 'loan') or inline Markdown/BPMN node inventory.
| Name | Required | Description | Default |
|---|---|---|---|
| bpmn | No | Inline Markdown node inventory / BPMN text to diagnose | |
| sample | No | Built-in sample workflow to diagnose |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It discloses the output format and input types but does not mention permissions, side effects, or limitations. The description adds value but is not exhaustive.
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?
Two sentences with no wasted words. The first sentence captures the core purpose and output, the second explains input options. Well front-loaded and efficient.
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?
The description explains the return format and input options adequately for a diagnostic tool with moderate complexity. However, it could be more explicit about input priority, error handling, or example outputs, especially since there is no output schema.
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% with descriptions for both parameters. The tool description clarifies that the inputs are alternatives ('or'), which adds useful semantic guidance beyond the schema's optional fields.
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 ('analyze') and resource ('agentic AI workflow') and clearly states the output format (per-node RED/AMBER/GREEN risk across three axes). It also mentions the incident ontology and input options, making the purpose unambiguous.
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 implies the tool is for diagnosing workflows but does not explicitly state when to use it versus alternatives. Since there are no sibling tools, the lack of explicit exclusions is acceptable, but more context could be added.
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!