terse
Related Servers
Alternatives to terse
- AlicenseAqualityBmaintenanceEnables encoding JSON into compact TOON format and decoding TOON back to JSON, reducing token usage for LLM prompts.213Apache 2.0
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible developer environments to shrink verbose tool outputs—test logs, git diffs, directory listings, and file dumps—before they reach the context window, preserving compiler errors, failure signatures, and decisive anchors. It runs either as direct callable tools or as a transparent proxy wrapping other MCP servers such as filesystem, git, or terminal providers.1MIT
- AlicenseAqualityAmaintenanceMCP server and local proxy that compresses LLM prompts, tool output, and replies to cut token cost, with a quality gate that reverts any step that does not save. Exposes llmtrim_compress, llmtrim_compress_text, and llmtrim_stats.3239Mozilla Public 2.0
- AlicenseAqualityCmaintenanceMCP proxy that compresses tool schemas on the fly. Up to 98% token reduction, 100% signal preserved verified after every compression. Zero LLM calls, fully deterministic.53MIT
- FlicenseBqualityDmaintenanceLocal MCP server for token optimization, providing tools to compress code/JSON, optimize prompts, and manage placeholder-based content redaction and hydration to reduce LLM token usage.5-
- AlicenseAqualityAmaintenanceAggregator MCP proxy that collapses N downstream MCP servers into 4 meta-tools with progressive tool discovery, and compresses large tool outputs (HTML→Markdown, JSON summarization) with full-output retrieval via read_more and a per-session token-savings report.4103 npm2MIT
- AlicenseNot gradedqualityCmaintenanceA local-first MCP server that reduces LLM token usage by intercepting, deduplicating, compressing, and optimizing MCP tool calls and responses.6 npmMIT
TDQS
Scored across 2 tools
demo_logs returns plain-text log data while demo_orders returns a JSON record array; the descriptions explicitly contrast the two formats and reference each other, leaving no ambiguity about which tool to use for a given output shape.
Both tools follow the exact same pattern: demo_ prefix plus a plural noun (logs, orders) in snake_case. There is no mixing of conventions or verb styles.
Two tools is slightly under the typical 3-15 range, but the server's apparent purpose is to provide exactly two demo output shapes (text and record array), so each tool earns its place without redundancy.
The set covers text and record-array shapes, but the descriptions mention terse's dictionary tier and tabularize behavior without providing a corresponding dictionary-shaped demo tool. Other potential shapes (e.g., nested data, errors) are also absent, leaving notable gaps for a demo server.