Samuelz® Business OS

Get connected workspace and access context

get_business_context

Read-onlyIdempotent

Read the connected workspace identity, discover the available Business core or find existing role positions. For records use get_business_funnel, get_business_goals or get_business_budgets.

Choose view=identity for current context/profile without catalog reads; omit names, domain and detail. Discovery is the default: names and domain intersect, detail=summary returns names/access and full adds descriptions/schemas without expanding permissions. Empty filtered results do not prove absence. This profile covers overview, goals and budgets. Use the separate CRM, Marketing, Policy, Sales or Accounting connection for those domains.

view=roles returns minimal live roleDirectory keys/titles, requires current work:read and Workspace read authority and accepts no catalog filters. Follow nextRoleKey as afterRoleKey while hasMore. Role discovery grants no allocation authority. profile.id is workspace-bound and opaque. missingScopes/access.nextAction identify unmet prerequisites. Authentication failure is an error; this read cannot sign in, switch tenants or grant access. Later actions recheck authority.

Input Schema

Name	Required	Description
`view`	No	identity reads this workspace's current profile without loading a capability catalog; omit all catalog filters. discovery returns profile and catalog with the supplied filters. roles lists existing role keys/titles with current work:read and Workspace read authority; it returns neither profile nor catalog. Omit for Business discovery or the other profiles' legacy default.
`limit`	No	roles only: page size, 1–100; omitted means 50.
`names`	No	Exact capability names to inspect. Unknown or out-of-profile names add no capabilities. Omit for all matching tools; an empty array selects none.
`detail`	No	summary (default) omits descriptions and schemas; full includes them, without making undisclosed tools callable.
`domain`	No	Filter by catalog domain within this connection's published toolset; never changes workspace or expands access. Omit to include matching tools from all domains in this surface.
`afterRoleKey`	No	roles only: copy roleDirectory.pagination.nextRoleKey. Seek strictly after that existing workspace position; pages are live, not a frozen snapshot.

Output Schema

Name	Required	Description
`scopes`	Yes
`profile`	No
`tenantId`	Yes
`roleDirectory`	No	Existing Work positions only. Keys/titles grant no allocation or management authority; no holders or policy contents are returned.
`capabilityCatalog`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 2, 2026

changedInput schema / allOf

Previous value: -[
-  {
-    "if": {
-      "properties": {
-        "view": {
-          "const": "identity"
-        }
-      },
-      "required": [
-        "view"
-      ]
-    },
-    "then": {
-      "not": {
-        "anyOf": [
-          {
-            "required": [
-              "names"
-            ]
-          },
-          {
-            "required": [
-              "domain"
-            ]
-          },
-          {
-            "required": [
-              "detail"
-            ]
-          }
-        ]
-      }
-    }
-  }
-]New value: +[
+  {
+    "if": {
+      "properties": {
+        "view": {
+          "enum": [
+            "identity",
+            "roles"
+          ]
+        }
+      },
+      "required": [
+        "view"
+      ]
+    },
+    "then": {
+      "not": {
+        "anyOf": [
+          {
+            "required": [
+              "names"
+            ]
+          },
+          {
+            "required": [
+              "domain"
+            ]
+          },
+          {
+            "required": [
+              "detail"
+            ]
+          }
+        ]
+      }
+    }
+  },
+  {
+    "else": {
+      "not": {
+        "anyOf": [
+          {
+            "required": [
+              "limit"
+            ]
+          },
+          {
+            "required": [
+              "afterRoleKey"
+            ]
+          }
+        ]
+      }
+    },
+    "if": {
+      "properties": {
+        "view": {
+          "const": "roles"
+        }
+      },
+      "required": [
+        "view"
+      ]
+    }
+  }
+]

addedInput schema / properties / afterRoleKey

Added value: +{
+  "description": "roles only: copy roleDirectory.pagination.nextRoleKey. Seek strictly after that existing workspace position; pages are live, not a frozen snapshot.",
+  "maxLength": 120,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "roles only: page size, 1–100; omitted means 50.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

changedInput schema / properties / view / description

Previous value: -"identity reads this workspace's current profile without loading a capability catalog; omit all catalog filters. discovery returns profile and catalog with the supplied filters. Omit for Business discovery or the other profiles' legacy default."New value: +"identity reads this workspace's current profile without loading a capability catalog; omit all catalog filters. discovery returns profile and catalog with the supplied filters. roles lists existing role keys/titles with current work:read and Workspace read authority; it returns neither profile nor catalog. Omit for Business discovery or the other profiles' legacy default."

changedInput schema / properties / view / enum

Previous value: -[
-  "identity",
-  "discovery"
-]New value: +[
+  "identity",
+  "discovery",
+  "roles"
+]

addedOutput schema / properties / roleDirectory

Added value: +{
+  "additionalProperties": false,
+  "description": "Existing Work positions only. Keys/titles grant no allocation or management authority; no holders or policy contents are returned.",
+  "properties": {
+    "coverage": {
+      "const": "registered_positions_live_pages",
+      "type": "string"
+    },
+    "grantsBusinessAuthority": {
+      "const": false,
+      "type": "boolean"
+    },
+    "pagination": {
+      "additionalProperties": false,
+      "properties": {
+        "hasMore": {
+          "type": "boolean"
+        },
+        "nextRoleKey": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "hasMore",
+        "nextRoleKey"
+      ],
+      "type": "object"
+    },
+    "positions": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "roleKey": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "roleKey",
+          "title"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "revision": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "revision",
+    "positions",
+    "pagination",
+    "coverage",
+    "grantsBusinessAuthority"
+  ],
+  "type": "object"
+}

AddedNov 1, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the bar is lower, yet the description still adds real behavior: this read cannot sign in, switch tenants or grant access, auth failure is an error, empty filtered results do not prove absence, and later actions recheck authority. That is substantive context beyond the annotation set, though the pacing and density make the disclosures harder to extract than they should be.

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

Conciseness3/5

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

Purpose and the identity-mode rule are front-loaded, but the body is a dense run-on stream that mixes pagination, auth failure, profile.id opacity and cross-domain routing without paragraph or list structure. Nearly every sentence carries information, yet the lack of grouping makes the description harder to scan than its length warrants.

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?

With an output schema present, the description need not explain return values, and it correctly stays focused on mode selection, authority prerequisites and pagination workflow. Coverage is strong for a three-mode read tool; only the undefined 'Business core' framing leaves a small gap in the agent's mental model.

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%, so the schema already documents all six parameters, including view, detail, names and domain. The description adds a little workflow guidance ('Follow nextRoleKey as afterRoleKey while hasMore') and reinforces the exclusivity of view=roles with other filters, but most of its parameter talk restates what the schema already says. 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?

The description opens with a specific verb and enumerates three distinct modes (identity, discovery, roles) and explicitly redirects record lookups to get_business_funnel, get_business_goals and get_business_budgets. The only weakness is jargon like 'Business core' that is never defined, but the mode enumeration makes the tool's function clear enough to select it.

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

Usage Guidelines5/5

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

Explicit when-to-use for each mode: view=identity for current context without catalog reads, discovery as the default, roles only when current work:read and Workspace read authority exist. It also states when NOT to use it — defer to the separate CRM, Marketing, Policy, Sales or Accounting connection for those domains — which is exactly the alternative-routing an agent needs.

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

All Samuelz® Business OS tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?