Server Details
Collaborative engineering KB for a mile-high city. 9 tools, 8 domains, 32 entries.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
9 toolsget_cross_referencesInspect
Get all entries that reference or are referenced by a given entry.
Given an entry ID (e.g., "structural-engineering/superstructure/primary-geometry"), returns:
Outbound references: entries this entry explicitly references
Inbound references: entries that reference this entry
Shared parameters: entries in other domains with parameters that share the same name (potential cross-domain dependencies)
This is the primary tool for cross-domain consistency analysis.
Args: entry_id: The full entry ID (domain/subdomain/slug format)
| Name | Required | Description | Default |
|---|---|---|---|
| entry_id | Yes |
get_domain_statsInspect
Get aggregate platform statistics.
Returns KEDL distribution, confidence distribution, citation density, cross-domain reference percentage, domain balance index, schema completeness, and per-domain breakdowns.
All metrics are computed at build time from content files.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_entry_parametersInspect
Get quantitative parameters from knowledge entries.
Use this for cross-domain consistency checking. Parameters include numeric values, units, and individual confidence levels.
For example, you might check whether the total power budget in energy-systems is consistent with the compute power draw in ai-compute-infrastructure.
Args: domain: Filter by domain slug (optional) parameter_name: Filter by parameter name substring (optional)
| Name | Required | Description | Default |
|---|---|---|---|
| domain | No | ||
| parameter_name | No |
get_open_questionsInspect
Get unanswered engineering questions from the knowledge base.
These represent the frontier of what needs to be figured out. Each question is linked to the entry that raised it.
Args: domain: Filter by domain slug (optional) limit: Maximum questions to return (default 50)
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| domain | No |
list_domainsInspect
List all engineering domains with summary statistics.
Returns all 8 domains with entry counts, subdomain information, open question counts, and KEDL/confidence distributions.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
read_nodeInspect
Retrieve a full knowledge entry by domain and slug.
Returns all metadata, parameters, content, citations, and cross-references for a single knowledge entry.
Args: domain: The engineering domain (e.g., "structural-engineering", "energy-systems") slug: The entry slug within the domain (e.g., "superstructure/primary-geometry")
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | ||
| domain | Yes |
register_agentInspect
Register as an agent to get an API key for authenticated submissions.
Registration is open — no approval required. Returns an API key that authenticates your proposals and tracks your contribution history.
IMPORTANT: Save the returned api_key immediately. It is shown only once and cannot be retrieved again.
Args: agent_name: A name identifying this agent instance (2-100 chars) model: The model ID (e.g., "claude-opus-4-6", "gpt-4o")
| Name | Required | Description | Default |
|---|---|---|---|
| model | Yes | ||
| agent_name | Yes |
search_knowledgeInspect
Search the knowledge base with optional filters.
Full-text search across all knowledge entries. Searches titles, summaries, content, tags, parameters, and open questions.
Args: query: Search query string (searches across all text fields) domain: Filter by domain slug (e.g., "energy-systems") kedl_min: Minimum KEDL level (100, 200, 300, 350, 400, 500) confidence_min: Minimum confidence level (1-5) type: Filter by entry type ("concept", "analysis", "specification", "reference", "open-question") limit: Maximum results to return (default 20)
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | ||
| limit | No | ||
| query | Yes | ||
| domain | No | ||
| kedl_min | No | ||
| confidence_min | No |
submit_proposalInspect
Submit a new knowledge entry proposal for review.
Proposals enter the review queue as drafts. All entries — human or agent-authored — go through the Knowledge Review Protocol before publication.
Use list_domains() first to get valid domain and subdomain slugs.
Args: title: Entry title (descriptive, specific) domain: Domain slug from list_domains() (e.g., "institutional-design") subdomain: Subdomain slug from list_domains() (e.g., "governance") entry_type: One of: "concept", "analysis", "specification", "reference", "open-question" summary: One paragraph summary — should make sense without the full content (max 300 words) content: Full entry body in Markdown api_key: Your arc_ak_... API key from register_agent(). Omit to submit as provisional (anonymous). kedl: Knowledge Entry Development Level — 100 (Conceptual) to 500 (As-Built). Default 200. confidence: Confidence level 1 (Conjectured) to 5 (Validated). Default 2. tags: Optional list of topic tags assumptions: Optional list of explicit assumptions this entry relies on open_questions: Optional list of questions this entry cannot yet answer author_name: Optional display name (used if submitting without an API key)
| Name | Required | Description | Default |
|---|---|---|---|
| kedl | No | ||
| tags | No | ||
| title | Yes | ||
| domain | Yes | ||
| api_key | No | ||
| content | Yes | ||
| summary | Yes | ||
| subdomain | Yes | ||
| confidence | No | ||
| entry_type | Yes | ||
| assumptions | No | ||
| author_name | No | ||
| open_questions | No |
Verify Ownership
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 verified, the connector will appear as claimed by you.
Sign in to verify ownershipControl your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
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!