Jsonify

Create workspace

create_workspace

Idempotent

Create an empty workspace when requested. Select organisation_id from get_context when more than one is available. Reuse the same idempotency_key on retries. Does not start collection or paid work.

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>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "create_workspace"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`idempotency_key`	Yes
`organisation_id`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare non-read-only, idempotent and non-destructive, but the description adds real behavior beyond them: the workspace is created empty, no collection or paid work is triggered, and retries are safe only if the same idempotency_key is reused. That retry caveat is exactly the kind of context annotations can't convey. It doesn't mention permissions or org-resolution failure modes.

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?

Four short sentences, front-loaded with the action, then the org-selection rule, the retry rule, and the scope caveat. Nothing is repeated and every sentence adds operational information.

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?

An output schema exists, so return values need not be described, and the description covers the two non-obvious behaviors (org selection and idempotency). The only gap is the absence of any guidance on the required name field or on what happens when no organisation_id is supplied.

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 description coverage is 0%, so the description must carry the load. It explains where organisation_id comes from (get_context) and the retry contract for idempotency_key, which is valuable, but the required `name` parameter gets no guidance and no length or uniqueness expectations are stated. Partial compensation only.

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 and resource ("Create an empty workspace") and the qualifier "empty" plus "Does not start collection or paid work" separates it from work-starting siblings like request_work and start_preparation. The phrase "when requested" is soft, but the resource is unambiguous.

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

Usage Guidelines4/5

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

Gives concrete routing guidance: pull organisation_id from get_context when multiple orgs exist, and reuse idempotency_key on retries. It also draws a boundary by noting the call does not kick off collection or paid work, implying where that belongs instead. No explicit statement of when NOT to create a workspace, so not a 5.

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

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