costwright
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COSTWRIGHT_DIRECT | No | Set to '1' to use direct channel (Authorization: Bearer) instead of RapidAPI (X-RapidAPI-Key). | 0 |
| COSTWRIGHT_API_KEY | Yes | Your API key for the costwright service. Required for check and certify tools. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| costwright_checkA | Statically analyze an LLM-agent repo (LangGraph / CrewAI / OpenAI-Agents-SDK) for runaway-budget risk WITHOUT running it. Builds a .py-only archive of the given local path and returns a worst-case budget summary: counts of certifiable / default_dependent / non_certifiable / runaway graph units and a pass|fail verdict. Use before deploying a workflow to catch missing token caps and while-True runaway drivers. |
| costwright_certifyA | Issue a tamper-evident, Ed25519-signed budget certificate for an agent repo (re-run server-side, logged to a public transparency log). Same input as costwright_check plus an optional label. Returns the cert_id, the signed certificate and a verify_url. Use to produce an auditable proof of a workflow's worst-case spend ceiling. |
| costwright_verifyA | Verify a previously issued costwright certificate by id (public, no key). Returns its state (valid|expired|revoked|signature_invalid), whether the signature checks out, and the certified result. |
| costwright_pubkeyA | Fetch costwright's active Ed25519 public keys (PEM) for offline signature verification of any certificate (public, no key). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: check analyzes budget risk, certify issues a certificate, pubkey retrieves public keys, and verify validates a certificate. No overlap in functionality.
All tools follow the consistent pattern 'costwright_' plus a verb or noun suffix (check, certify, pubkey, verify), making them easy to distinguish and predict.
With 4 tools, the server is well-scoped for its purpose of budget certification. Each tool is necessary and sufficient for the core workflow.
The set covers the essential operations: checking, certifying, verifying, and key retrieval. Minor gaps like revocation or listing are not critical for the primary use case.