Skip to main content
Glama
arc-mcp

ARC-1

by arc-mcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to ARC-1

No user-submitted related servers found.

    Related Servers

    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.1/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool has a distinct top-level theme (read, search, navigate, context, diagnose, lint, manage, transport), but there is real overlap: SAPContext explicitly says to use it 'instead of SAPRead', SAPNavigate references overlaps with SAPContext usages, and SAPDiagnose 'syntax' overlaps with SAPRead(type='SYNTAX'). Extensive cross-referencing and decision rules mitigate the confusion, but an agent must read carefully to route correctly.

    Naming Consistency5/5

    All 8 tools follow a uniform 'SAP' + singular-verb pattern (SAPNavigate, SAPContext, SAPDiagnose, SAPLint, SAPManage, SAPRead, SAPSearch, SAPTransport). Predictable and readable throughout with no deviations.

    Tool Count4/5

    Eight tools is a good, well-scoped count for an SAP development assistant. However each 'tool' carries a very large action namespace (SAPDiagnose and SAPManage each expose 20+ actions), making the effective surface heavier than the count suggests.

    Completeness3/5

    The read/search/navigate/diagnose/transport surface is broad, but the write side is missing: descriptions repeatedly reference SAPWrite, SAPActivate, and API_STATE writes that are not present in this set, creating dead-end workflows (e.g. quickfix stops at apply_quickfix with 'write via SAPWrite').

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources