Skip to content

v0.11.7 — Glama TDQS overhaul

Choose a tag to compare

View all tags
@I4cTime I4cTime released this 27 Apr 11:30
v0.11.7
3f3f354
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Glama Tool Definition Quality Score (TDQS) overhaul

Every one of the 44 MCP tools now ships a 3-sentence description hitting all six Glama TDQS dimensions:

  1. Purpose — what the tool does, in one sentence.
  2. Usage guidelines — when to use it, explicitly disambiguated against sibling tools.
  3. Behavioral transparency — side effects (mutations, audit logs, network calls), idempotency, and the exact return shape.

The server-level TDQS score weights the per-tool minimum at 40% (60% mean / 40% min), so this release specifically targets lifting the worst per-tool descriptions to drag the floor up.

Changed

  • All 44 MCP tool descriptions rewritten using the 3-sentence template.
  • commonSchemas (scope, projectPath, env, teamId, orgId) .describe() strings now include formats, defaults, conditional requirements, and concrete examples.
  • Per-tool Zod .describe() strings tightened across all 10 tool files.
  • README MCP tables resynced with the new one-liners.
  • feature-docs-sync.mdc and release-process.mdc rules updated for the moved-out marketing site (qring.i4c.studio).

Notes

  • No runtime / MCP wire-format changes. Tool names, parameter names, parameter types, and return shapes are unchanged. Existing agents and integrations will simply see longer, clearer descriptions on the next tools/list refresh.
  • After this release publishes, trigger a Glama re-sync from the admin panel so the new TDQS scoring run picks up the improved descriptions.
  • Marketing site sync (qring.i4c.studio) ships separately.

Install

npm install -g @i4ctime/q-ring@0.11.7
# or
brew upgrade i4ctime/tap/qring

Verify

qring --version    # should print 0.11.7
qring --help
Assets 2
Loading