OrgLines

Get workspace AI protocol

get_workspace_protocol

Read-only

CALL THIS FIRST in every session, before any other tool. It returns how to operate in this OrgLines workspace: the versioned SYSTEM rules, then EITHER the owner's own instructions OR — for a workspace that has not set any — the default onboarding protocol that tells you how to warm-start a new user (interview → file their data). Without reading it first you will miss the onboarding flow and the workspace's rules. It is the same text delivered in the MCP initialize instructions, so a client that lost those (or wants a mid-session refresh) re-fetches it here; it reflects any change made in this session with NO reconnect. Read-only. protocol_source tells you whether you're on the owner's custom protocol or the default onboarding one.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_workspace_protocol"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, non-destructive, closed-world), and the description adds genuinely new behavior: contents of the response, that it mirrors the MCP initialize instructions, that it reflects in-session changes with no reconnect, and what protocol_source indicates.

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

Conciseness4/5

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

Front-loaded with the action directive and generally dense with information. The sentence "Without reading it first you will miss the onboarding flow" partially restates the opening imperative, making it slightly longer than needed.

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

Completeness5/5

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

No output schema exists, and the description compensates by describing what is returned and how to interpret protocol_source. For a zero-parameter bootstrap tool with full annotation coverage, nothing an agent needs to call it correctly is missing.

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?

Zero parameters, so the baseline is 4. The description instead spends its detail on the return shape (protocol_source, system vs. owner vs. default protocol), which is useful but belongs to output semantics rather than parameters.

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 names a specific resource and its contents: "versioned SYSTEM rules, then EITHER the owner's own instructions OR ... the default onboarding protocol." It also distinguishes itself from get_workspace_settings/set_workspace_instructions by being the read-first bootstrap text rather than a settings editor.

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?

Gives an explicit imperative ("CALL THIS FIRST in every session, before any other tool") plus concrete alternative conditions: a client that lost MCP initialize instructions, or wants a mid-session refresh. The downside of skipping it is stated directly.

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

All OrgLines 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?