Cloudlabels

Create sheet

create_sheet

Create a new item sheet in this organization. Name is required. Confirm the barcode standard with the user before creating the sheet. barcode_standard is optional. If it is omitted, the sheet uses the workspace standard. The response says which standard was stored. barcode_standard_stored is false when the standard could not be saved. Optional catalog:true creates the empty sheet and turns Catalog on. The first catalog sheet uses applyPreset, which also moves defaultSheetNumber to the new sheet. Later catalog sheets use setSheetCatalogEnabled. preset_applied is true only when the preset was actually applied. If enable or preset fails after the sheet is created, the new sheet is deleted so a retry does not create a duplicate. Decide catalog vs a plain sheet first. Does not accept an organization id. Honors the plan sheet limit. Does not change existing sheets or barcode values. Optional idempotency_key. Omit this field when it is not used. Null, an empty string, or only spaces are also treated as omitted. Use a unique value such as a UUID. The same key and the same arguments return the stored result for 24 hours and set idempotent_replay to true. A key still in progress is rejected until the lease expires (15 minutes by default). The same key can also stay reserved until the lease expires (15 minutes by default) after a call failed after writing rows, so check whether those rows were saved before trying again. The same key with different arguments is rejected. A stored result over 200 KB is replaced by a short summary of ids and counts.

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_sheet"
  }
}

Input Schema

Name	Required	Description
`name`	Yes
`catalog`	No
`description`	No
`idempotency_key`	No	Optional. Omit this field when it is not used. An empty string is also treated as omitted. Use a unique value such as a UUID when you send one. Same key and same arguments return the stored result for 24 hours in this organization, with idempotent_replay true. A different payload is rejected.
`barcode_standard`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A3.9/5.0

Behavior5/5

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

With annotations present the bar is lower, yet the description goes well beyond them: it discloses the rollback guarantee (the new sheet is deleted if enable or preset fails), the plan sheet limit, that existing sheets and barcode values are untouched, and the exact response semantics of barcode_standard_stored, preset_applied, idempotent_replay. The idempotency contract (24h replay, 15-minute lease, conflicting-payload rejection, 200 KB truncation) is unusually well specified and is consistent with idempotentHint=false, which correctly means no implicit idempotency.

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?

It is a single dense run-on paragraph with no grouping, and content is duplicated — the 15-minute lease is stated twice in nearly identical wording, and several idempotency rules restate what the idempotency_key schema description already says. The most important facts (required name, catalog decision) are near the front, which saves it, but pruning would materially help.

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 5-parameter mutation tool with no output schema, it covers nearly everything an agent needs: side effects, failure/rollback behavior, response flags, idempotency edge cases, and limits. The remaining hole is the undocumented `description` field and no statement about what the success payload contains besides the two named flags.

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 only 20%, so the description must carry the parameter burden and mostly does: name is required, barcode_standard is optional with a documented default (workspace standard) plus a confirmation workflow, catalog:true turns Catalog on and triggers applyPreset versus setSheetCatalogEnabled, and idempotency_key is fully explained. The one gap is the `description` parameter, which is never mentioned in either the schema or the description.

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 opening sentence gives a specific verb and resource ("Create a new item sheet in this organization") plus scope constraints (no organization id, plan sheet limit, does not touch existing sheets or barcode values). It is clear what the tool does, but it never names the neighboring operations an agent might confuse it with (create_item, adopt_catalog_sheet, enable_catalog_sheet), so sibling differentiation is left implicit.

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?

"Decide catalog vs a plain sheet first" and "Confirm the barcode standard with the user before creating the sheet" are genuine pre-call rules, which is more than nothing. However, no alternative tool is named and no when-not-to-use condition is given (e.g., when to adopt or enable an existing catalog sheet instead), so guidance is implied rather than explicit.

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

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