Skip to main content
Glama
Sign In
mqdh-mcp

mqdh-mcp

by thankyoucoinbase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

select_org

Set the active developer organization by ID or name so subsequent app and release-channel actions apply to the correct organization, with the choice saved across sessions.

Instructions

Select the active developer organization (by id or name). Saved across sessions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "org": "<org>"
    },
    "name": "select_org"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesOrganization id or name (partial match ok)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description does carry one valuable behavioral disclosure: the selection is persisted across sessions, meaning a global state mutation. It omits what happens on an ambiguous partial match, whether the org is validated to exist, and what the call returns, which matters for a state-changing tool with zero annotation coverage.

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?

Two short sentences, zero filler, with the core action and the persistence side effect front-loaded.

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 a one-parameter tool with no output schema, the description covers the action, accepted inputs, and the cross-session persistence. Only the ambiguity/validation behavior on partial matches is left unstated.

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

Parameters3/5

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

Schema coverage is 100% and the schema already documents 'Organization id or name (partial match ok)'; the description only restates 'by id or name' and adds no tie-breaking or ambiguity behavior. Baseline 3 is appropriate.

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

Purpose4/5

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

States a specific verb and resource ('Select the active developer organization') plus the accepted identifier forms, so the agent knows this sets active state rather than listing orgs. It doesn't explicitly name list_orgs as the discovery sibling, which keeps it from a 5.

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

Usage Guidelines3/5

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

'Select the active...' plus 'Saved across sessions' implies the tool is used to pin a working context before other calls, but there is no explicit when-to-use/when-not or guidance to call list_orgs first when the org id is unknown.

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

Deploy Server

Other Tools