Skip to main content
Glama
vigmarcarlo

ontoprune-mcp

by vigmarcarlo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ontoprune-mcp

No user-submitted related servers found.

    Related Servers

    • redcon

      natiixnt
      F
      license
      A
      quality
      A
      maintenance
      Deterministic repository context packing for AI coding agents: selects, compresses, and budgets only the files a task needs. Measured 83% fewer input tokens at the same task coverage, fully local, no LLM in the loop.
      9
      9
      -

    • tokensense

      AayushKumbhare
      A
      license
      Not graded
      quality
      B
      maintenance
      Model-agnostic context management middleware for LLM-powered workflows, providing persistent selective memory across sub-conversations using RAG over embedded summaries.
      MIT

    • genpark-agentic-prompt

      Alpha-Park
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to deterministically shrink multi-turn conversation history and prompts by stripping verbose boilerplate and filler tokens while preserving critical tool parameters and named entities. This lets users cut inference costs by roughly 40-60% without losing essential context, running either as a native MCP server over JSON-RPC stdio or as an importable zero-dependency Python module.
      7
      MIT
    • genpark-meta-muse-episodic-memory-graph-mcp by alphaparkinc

      genpark-meta-muse-episodicofficial

      alphaparkinc
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to combine ambient multimodal perception, continuous episodic memory, and recency-decay context briefing for fast deterministic decisions and safe tool routing. It integrates with MCP clients to reduce unnecessary frontier LLM calls while enforcing token budgets and local-first memory retention.
      7
      MIT
    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 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: prune_context extracts a compact contract from source code, while verify_response validates LLM-generated code against such a contract. Their descriptions and argument sets make the boundary unambiguous.

    Naming Consistency5/5

    Both names follow a consistent verb_noun pattern in snake_case: prune_context and verify_response. There are no mixed conventions or vague verbs.

    Tool Count4/5

    Two tools is slightly below the typical 3-15 sweet spot, but each tool is substantial, non-redundant, and directly supports a focused extract-and-verify workflow. The set does not feel bloated or padded.

    Completeness4/5

    The pair covers the core lifecycle of extracting a contract and verifying code against it, with flexible input options for files or rendered contracts. Minor gaps exist for symbol discovery, batch pruning, or contract management, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources