Skip to content

Release v0.11.7#57

Merged
I4cTime merged 2 commits intomainfrom
develop
Apr 27, 2026
Merged

Release v0.11.7#57
I4cTime merged 2 commits intomainfrom
develop

Conversation

@I4cTime
Copy link
Copy Markdown
Owner

@I4cTime I4cTime commented Apr 27, 2026

Release v0.11.7

This is the release PR — it bundles the v0.11.7 work merged into develop and ships it to main, which triggers the npm + MCP Registry publish workflow on tag push.

What's in this release

A documentation-quality release: every one of the 44 MCP tools now ships a 3-sentence description hitting all six Glama Tool Definition Quality Score (TDQS) dimensions (purpose, when-to-use vs. siblings, side-effects/audit/network, parameter semantics, conciseness, returns), and shared parameter schemas (scope, projectPath, env, teamId, orgId) plus per-tool Zod .describe() strings now include formats, defaults, and concrete examples.

The server-level TDQS 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 a 3-sentence template (purpose / when-to-use vs. siblings / side-effects + returns).
  • commonSchemas (src/mcp/tools/_shared.ts) .describe() strings now include formats, defaults, and conditional requirements.
  • README MCP tables resynced with the new one-liners.
  • feature-docs-sync.mdc and release-process.mdc rules updated to cover the moved-out marketing site (qring.i4c.studio) — explicit cross-repo file map and downstream-sync table.

Notes

  • No runtime / MCP wire-format changes. Tool names, parameter names, parameter types, and return shapes are unchanged. Existing agents will simply see longer, clearer descriptions on next tools/list refresh.
  • Marketing site sync is a separate PR in qring.i4c.studio (not enforced by this repo's CI; tracked by release-process.mdc downstream-sync table).
  • After this PR merges, push tag v0.11.7 from main to fire publish.yml (npm + MCP Registry via OIDC), then trigger a Glama re-sync from the admin panel.

Version consistency

File Version
package.json 0.11.7
server.json (version) 0.11.7
server.json (packages[0].version) 0.11.7
cursor-plugin/.cursor-plugin/plugin.json 0.11.7
.cursor-plugin/marketplace.json 0.11.7

Test plan

All checks already green on develop from PR #56:

  • pnpm run typecheck
  • pnpm run lint ✓ (max-warnings 0)
  • pnpm run build
  • pnpm run test:ci ✓ (24 files / 164 tests)
  • CodeQL analyze (javascript-typescript)

Squash-merge recommended.

🤖 Generated with Claude Code

Made with Cursor

I4cTime and others added 2 commits April 27, 2026 20:24
All 44 tools now ship a 3-sentence description hitting the six Glama
Tool Definition Quality Score dimensions (purpose, when-to-use vs.
siblings, side-effects/audit/network, parameter semantics, conciseness,
returns). Common parameter schemas (`scope`, `projectPath`, `env`,
`teamId`, `orgId`) and per-tool Zod `.describe()` strings now include
formats, defaults, and concrete examples to lift the per-tool minimum
score that dominates the server-level grade (60% mean / 40% min).

- src/mcp/tools/_shared.ts: enriched commonSchemas describe() strings
- src/mcp/tools/{secrets,project,tunnel,teleport,audit,validation,hooks,
  tooling,agent,policy}.ts: 44 tool descriptions rewritten + parameter
  describe() strings tightened
- README.md: MCP tables resynced with new one-liners
- CHANGELOG.md: 0.11.7 entry
- package.json / server.json / plugin.json / marketplace.json: 0.11.7

No runtime / MCP wire-format changes — agents will see longer, clearer
tool descriptions on next tools/list refresh; tool names, parameters,
and return shapes are unchanged.

Test plan:
- pnpm run typecheck ✓
- pnpm run lint ✓ (max-warnings 0)
- pnpm run build ✓
- pnpm run test:ci ✓ (24 files / 164 tests)

Made-with: Cursor
feat: v0.11.7 — Glama TDQS overhaul for all 44 MCP tools
@I4cTime I4cTime merged commit 3f3f354 into main Apr 27, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant