Qumge: Agent Capabilities & Skills

become_developer

Open a developer account for the user (needs their qumge key). There is no review and no waiting: it takes effect immediately, and publish_cap works right after. Give a display name and an ISO country code; the country decides tax and payout rails later. Payout details and legal name are only needed when the user actually withdraws money.

Input Schema

TableJSON Schema

Name	Required	Description
`country`	Yes	ISO code like "US" or "CN" (a full country name also works).
`username`	No	Required if the account has no username yet: 3–30 letters, digits, _ or -. It becomes the public page /u/<username>.
`qumge_key`	No	Optional: your Qumge API key, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back.
`entity_type`	No	individual (default) or company.
`display_name`	Yes	The name shown on their app pages.
`social_links`	No	Up to 6 public URLs (X, GitHub, LinkedIn, their website). The kind is guessed from the domain.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	No
`country`	Yes
`display_name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 30, 2026

addedInput schema / properties / username

Added value: +{
+  "description": "Required if the account has no username yet: 3–30 letters, digits, _ or -. It becomes the public page /u/<username>.",
+  "type": "string"
+}

Changed1 schema field changedSep 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "country": {
+      "type": "string"
+    },
+    "display_name": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "display_name",
+    "country"
+  ],
+  "type": "object"
+}

AddedSep 26, 2026

TDQS

A4.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does well: it discloses that there is no review or wait, that it takes effect immediately, that publish_cap becomes usable right after, and that country choice determines tax and payout rails later. It omits idempotency/repeat-call behavior and what happens if the user is already a developer.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tightly written sentences, front-loaded with the core action and immediately followed by the behavioral reassurance (no review, immediate effect) and the deferred-requirement note. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an account-creation tool with an output schema and full param coverage, the description supplies the prerequisites, side effects, and downstream dependency the agent needs. The main gap is the absence of guidance on repeat invocation or existing-account handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning beyond the schema: it explains that country drives tax and payout rails downstream and that display name/country are the immediate requirements, while qumge key and legal details are contextual.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Open a developer account for the user') and situates it in the workflow by noting 'publish_cap works right after', which cleanly separates it from the publish/payout siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear context for when this applies (onboarding a user before publishing) and states a prerequisite (the qumge key), plus it clarifies that payout details and legal name are deferred to withdrawal time. There is no explicit 'when-not' case, such as what to do if the account already exists.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Qumge: Agent Capabilities & Skills tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?