Skip to main content
Glama

Qumge: Agent Capabilities & Skills

submit_cap

Take one of the developer's Caps live. Nothing is reviewed before launch and nobody approves it: when the three code-checked items pass (signature, end-to-end, price book), this publishes the Cap immediately and agents can call it — and be charged — from then on. Run test_cap first (it records signature + end-to-end; the price book is recorded when it saves). Qumge spot-checks docs and support afterwards and can suspend the Cap. Needs the developer's Qumge key. (Older clients may still call this tool as submit_app_review.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesThe Cap's slug.
qumge_keyNoOptional: your Qumge API key, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYes
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"The cap's slug."New value: +"The Cap's slug."
  2. Changed1 schema field changed
    • addedInput schema / properties / qumge_key
      Added value: +{
      +  "description": "Optional: your Qumge API key, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back.",
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "slug": {
      +      "type": "string"
      +    },
      +    "status": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "slug",
      +    "status"
      +  ],
      +  "type": "object"
      +}
  4. Added

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources