Corbelworks Agent Reliability
Server Details
Preflight agent claims, issue checkout links, and verify signed Corbelworks action receipts.
- 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
Score is being calculated. Check back soon.
Available Tools
3 toolspurchase_agent_reliability_scanBuy a Fixed-Scope Agent Reliability ScanBRead-onlyInspect
Get the fixed $149 Stripe checkout link for an Agent Reliability + Action-Receipt Scan; the signed link receipt explicitly records payment_status=not_paid.
| Name | Required | Description | Default |
|---|---|---|---|
| workflow_summary | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| receipt | Yes | |
| instruction | No | |
| checkout_url | Yes | |
| payment_status | Yes | |
| service_reserved | Yes |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true, implying a read operation, but the description and title indicate a purchase (write). This is a direct contradiction; the description does not resolve the inconsistency.
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 concise at one sentence, front-loading the key output (checkout link). However, it could be more structured by separating purpose and receipt details.
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?
Despite having an output schema, the description only vaguely mentions a 'signed link receipt' without detailing the schema fields. The contradiction with annotations and lack of parameter guidance make the tool incomplete for an agent.
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 schema has one undocumented parameter (workflow_summary) with 0% schema description coverage. The description adds no information about this parameter, leaving its semantics entirely unclear.
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 tool returns a fixed $149 Stripe checkout link for a specific scan. The verb 'Get' and resource 'checkout link' are specific, and the purpose is distinct from siblings 'reliability_preflight' and 'verify_action_receipt'.
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 use for purchasing a scan (title says 'Buy'), but provides no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives or prerequisites, but the context of a fixed-price link makes usage clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
reliability_preflightAgent Reliability Evidence PreflightRead-onlyInspect
Find false-green risk by linting agent claims against evidence, freshness, and external-receipt requirements; returns a signed Corbelworks action receipt.
| Name | Required | Description | Default |
|---|---|---|---|
| manifest | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| receipt | Yes | |
| preflight | Yes |
verify_action_receiptVerify a Signed Action ReceiptRead-onlyIdempotentInspect
Verify a Corbelworks Ed25519 action receipt, payload digest, and signature against the published public key.
| Name | Required | Description | Default |
|---|---|---|---|
| receipt | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| valid | Yes | |
| reason | Yes | |
| signed_payload_sha256 | No |
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!