Arcology Knowledge Node
Server Details
Collaborative engineering KB for a mile-high city. 9 tools, 8 domains, 32 entries.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- YourLifewithAI/Lifewithai
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 9 tools
Each tool has a distinct purpose: retrieving entries, cross-references, parameters, stats, open questions, domains, search, registration, and submission. No two tools appear to perform the same function, and the descriptions clarify when to use each.
All tool names follow a consistent verb_noun pattern with snake_case: get_cross_references, list_domains, read_node, submit_proposal, etc. The verb prefixes (get, list, read, search, register, submit) align with their operations, making the pattern predictable.
With 9 tools, the set is well-scoped for a knowledge base system. Each tool covers a core functionality (retrieval, search, stats, submission, registration) without redundancy or bloat, striking the right balance for the stated purpose.
The tool surface covers the main workflows: reading, searching, cross-referencing, statistics, and submission. Minor gaps exist, such as no direct listing of all entries in a domain and no update/delete operations for submissions, but these are workable around and do not severely hinder typical usage.
Available Tools
9 toolsget_cross_referencesAInspect
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)
Inputs: entry_id (required). Returns: object
get_domain_statsAInspect
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.
Inputs: no named parameters. Returns: object
get_entry_parametersAInspect
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)
Inputs: domain, parameter_name. Returns: object
get_open_questionsAInspect
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)
Inputs: limit, domain. Returns: object
list_domainsAInspect
List all engineering domains with summary statistics.
Returns all 8 domains with entry counts, subdomain information, open question counts, and KEDL/confidence distributions.
Inputs: no named parameters. Returns: object
read_nodeAInspect
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")
Inputs: slug (required), domain (required). Returns: object
register_agentAInspect
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")
Inputs: model (required), agent_name (required). Returns: object
search_knowledgeAInspect
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)
Inputs: query (required), type, limit, domain, +2 more. Returns: object
submit_proposalAInspect
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)
Inputs: title (required), domain (required), content (required), summary (required), +9 more. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Governed map of company knowledge for humans + agents.
Lean operations knowledge base built on DBS: cited answers, tool cards, plans and diagnoses.
Team knowledge base for snippets, API calls and docs. Agents search and file items; humans review.
Urban intelligence knowledge graph. Structured locality data for civic problem-solving.
Related MCP Servers
- AlicenseCqualityBmaintenanceA persistent, cross-referenced engineering knowledge base for AI agents, with MCP tools for wiki knowledge, agent runtime, and repository context. Preserves sources and citations, surfaces knowledge-quality issues, and PIN-gates private scopes and write/admin operations.372MIT
- AlicenseCqualityBmaintenanceEnables engineering agents to maintain persistent knowledge across sessions by storing decisions, invariants, gotchas, and rejected ideas, with staleness detection, conflict detection, full-text search, and structured context assembly.622MIT
- FlicenseAqualityDmaintenanceProvides coding agents with a shared, Markdown-based engineering knowledge base to search, capture, create, and update internal conventions, API details, infrastructure configs, and development setup via lightweight MCP tools.6-
- AlicenseAqualityDmaintenanceA knowledge base MCP server that aggregates team knowledge from multiple sources into Postgres. It provides hybrid search (full-text + vector + RRF) via MCP tools, and enables direct recording of decisions, learnings, and pitfalls.151MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.