Skip to main content
Glama
MCP Dokploy Online
by igoruam

user-checkUserOrganizations

Read-onlyIdempotent

Checks the organizations associated with a user ID to verify membership and access scope.

Instructions

GET /user.checkUserOrganizations

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": {
      "userId": "<userId>"
    },
    "name": "user-checkUserOrganizations"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that: it does not say whether the check returns a boolean, a list of organizations, or throws when the user has none, nor what unknown userIds produce. No contradiction with annotations exists, but no value is added either.

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

Conciseness2/5

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

It is short and front-loaded, but only because it is an unembellished route echo rather than a deliberate summary. Nothing is wasted, yet nothing useful is present—under-specification, not conciseness.

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

Completeness2/5

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

With one undocumented parameter and no output schema, the description is the only place to explain what is checked and what comes back, and it explains neither. An agent cannot reliably decide when to call it or how to interpret the result.

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

Parameters2/5

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

Schema description coverage is 0% for the single required userId parameter, so the description must carry the weight and does not. It never clarifies whether userId refers to a user ID, email, or slug, nor whether the caller can check another user's organizations or only their own.

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

Purpose2/5

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

The description is only the raw route 'GET /user.checkUserOrganizations', which restates the tool name rather than describing the operation. An agent can infer it inspects a user's organization memberships, but there is no verb-level explanation of what is checked or what result is produced, and nothing distinguishes it from siblings like user-get or user-one.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no prerequisites, and no mention of any alternative tool. The agent must guess whether this is the right tool versus user-get, user-one, or user-getPermissions.

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