Static linter for CLAUDE.md-style agent constitution files: 10 operational-guardrail checks.
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.9/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of confusion between tools.
With a single tool, naming consistency is trivially maintained via the clear verb_noun pattern 'lint_constitution'.
The single tool is well-scoped for the server's narrow purpose of linting constitution files, bundling 10 checks into one cohesive operation.
The tool covers the key heuristic checks for CLAUDE.md-style constitution files as described, leaving no obvious gaps for its pattern-matching scope.
lint_constitutionAInspectHeuristic checker for CLAUDE.md-style autonomous-agent constitution files — 10 checks against operational-guardrail patterns (authority order, spend limit, injection defense, secrets handling, escalation, ledger discipline, self-modification guard, honest reporting, session ritual, referenced-state-files). Pattern-matching, not comprehension.
| Name | Required | Description | Default |
|---|---|---|---|
| content | Yes | The full markdown text of a CLAUDE.md-style constitution file |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that the checker is pattern-matching (not comprehension) and lists the 10 checks performed. No annotations exist, so the description carries full burden; it adequately informs the agent of the tool's heuristic nature and scope.
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?
A single sentence front-loaded with the main action, followed by a parenthetical list of checks. It is efficient and well-structured, though the list slightly reduces readability.
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 simple lint tool with one parameter and no output schema, the description covers the purpose, the 10 checks, and the heuristic nature. It leaves some ambiguity about the output format, but overall it is sufficient for an agent to use the tool correctly.
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?
There is one parameter ('content') with full schema coverage. The description adds context about what the tool does but does not enhance the parameter's meaning beyond the schema's description. Baseline 3 is appropriate.
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 it is a heuristic checker for CLAUDE.md-style constitution files, listing 10 specific checks. It identifies the resource and action precisely, and despite no siblings, the description is self-contained and 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 usage for checking constitution files but provides no explicit guidance on when or when not to use it, and no alternatives are mentioned. The context is clear but lacks exclusions or conditions.
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!