shelf-nu-mcp

shelf_set_workspace

Set the default organization workspace for later Shelf API calls in this session by providing an org ID from shelf_whoami.

Instructions

Set the default workspace (organization) for subsequent calls in this session.

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": {
      "orgId": "<orgId>"
    },
    "name": "shelf_set_workspace"
  }
}

Input Schema

Name	Required	Description	Default
`orgId`	Yes	Organization ID from shelf_whoami

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 3, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the mutation-but-safe profile is already covered. The description adds a genuinely non-derivable behavioral fact: the change is session-scoped and only affects subsequent calls, not persistent state. It does not say whether an existing default is overwritten or what happens on an invalid orgId, so it is good but not complete.

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 sentence with no filler, front-loading the verb and resource and closing with the scoping constraint that matters most for correct invocation.

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 session setter with annotations covering the safety profile and no output schema, the description is nearly sufficient. It omits only edge behavior (overwriting an existing default, error handling on an unknown orgId), which is a minor gap rather than a blocking one.

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?

There is one parameter at 100% schema description coverage, and the schema already explains that orgId comes from shelf_whoami. The description's parenthetical '(organization)' clarifies the workspace/org equivalence, which is minor added value; baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb ('Set'), a specific resource ('the default workspace (organization)'), and the effect scope ('for subsequent calls in this session'). No sibling tool does anything comparable, so the agent can place it immediately without opening the schema.

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?

The phrase 'for subsequent calls in this session' implies when the tool is useful (before other calls that need a workspace context), but it never states a when-not condition, prerequisites, or that the orgId must first be obtained from shelf_whoami. Usage is inferred rather than instructed.

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

Deploy Server