Skip to main content
Glama
Sign In

Nutcracker

by com.heynutcracker
OverviewDiscussionsAdmin

Create space

create_space

Make a space when list_spaces has none that fits. If this place already has a space with the name, that one comes back with created: false instead of a second. A sub-space (parent_id) also reads its parent's pinned docs and elements, and takes its parent's scope. Otherwise scope decides who sees it: personal, the default, is your human alone; team is everyone in the workspace, so make a team space only when your human agrees.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
scopeNoWho sees a top-level space. Default personal.
parent_idNoA space id from list_spaces, to make a sub-space of it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare it is a non-destructive, non-open-world write; the description goes well beyond that by disclosing idempotency ('created: false instead of a second'), inherited visibility/scope for sub-spaces, and what each scope value exposes to whom. Those are non-obvious side effects an agent could not infer from readOnlyHint=false.

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?

Three sentences, front-loaded with the decision rule, then duplicate-handling, then inheritance/scope. Dense but every clause carries information; the parent_id sentence is slightly overloaded with two inheritance facts in a row.

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 write tool with no output schema, it covers the essentials: when to call, idempotent duplicate behavior (including the created flag), and scope/inheritance semantics. It does not mention any permission or authorization requirements for creating spaces, which is the main remaining gap.

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?

Schema coverage is 67%, and the description usefully explains the real-world consequences behind both documented enums: personal is 'your human alone' and is the default, team is 'everyone in the workspace'. parent_id gains the strongest added meaning – sub-spaces inherit the parent's pinned docs, elements, and scope. It adds nothing for 'name' beyond its obvious intent, but the schema already constrains it.

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 concrete verb+resource ('Make a space') and immediately scopes it against the sibling list_spaces. An agent can tell this apart from list_spaces/list_space without opening either schema.

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 gating rule: use it 'when list_spaces has none that fits', which names the alternative and the condition that selects this tool. It also adds a consent precondition for team spaces ('only when your human agrees'), which is genuine when-to-use guidance rather than restating the name.

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

All Nutcracker toolsInspect
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