Skip to main content
Glama
Sign In
nexterm-mcp

nexterm-mcp

by X1pheR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

nexterm_get_organization_member_permissions

Read-onlyIdempotent

Retrieve the effective permissions for a specific member within an organization by using organization and account IDs.

Instructions

Read one organization's effective member permissions.

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": {
      "organization_id": "<organization_id>",
      "account_id": "<account_id>"
    },
    "name": "nexterm_get_organization_member_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idYes
organization_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds only the word 'effective', hinting at computed/inherited permissions, but does not disclose how permissions are resolved or what a missing member yields.

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?

A single front-loaded sentence with no filler. Every word earns its place.

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?

No output schema exists, so the description should describe what 'permissions' returns (role, scopes, booleans). It leaves the return shape and the error behavior for a non-member entirely undefined, which is inadequate for a lookup tool.

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 both required parameters, so the description must carry the meaning. It implies organization_id and a member identifier but never clarifies that account_id is the member's account and not, say, an invitation or membership record id.

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 (Read) and resource (one organization's effective member permissions). It is distinguishable from list_organization_members and get_organization, though the word 'effective' is unexplained.

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

Usage Guidelines2/5

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

No guidance on when to use this versus nexterm_list_organization_members or nexterm_get_organization, and no prerequisites such as requiring membership or admin rights. Usage is only inferable from the name.

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