Skip to main content
Glama
Sign In

Tilebox

by com.tilebox
OverviewDiscussionsAdmin

Create storage location

create_storage_location

Register an existing bucket, container, or directory. Does not create cloud resources.

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>",
      "reference": "<reference>"
    },
    "name": "create_storage_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
referenceYes

Output Schema

NameRequiredDescriptionDefault
idYes
nameYes
typeYes
locationYes
referenceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / reference / properties / path / description
      Previous value: -"filesystem directory path"New value: +"local directory path"
    • changedInput schema / properties / reference / properties / type / description
      Previous value: -"storage type: aws_s3_bucket, gcs_bucket, azure_blob, or filesystem"New value: +"storage type: aws_s3, gcs, azure_blob, or local"
    • changedOutput schema / properties / reference / properties / path / description
      Previous value: -"filesystem directory path"New value: +"local directory path"
    • changedOutput schema / properties / reference / properties / type / description
      Previous value: -"storage type: aws_s3_bucket, gcs_bucket, azure_blob, or filesystem"New value: +"storage type: aws_s3, gcs, azure_blob, or local"
  2. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the write-but-non-destructive profile is covered structurally. The description adds one useful behavioral fact beyond that: this only registers metadata and does not create cloud resources. It says nothing about duplicate handling, permissions required, or what happens on re-registration, which matters given idempotentHint=false.

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?

Two sentences, zero filler, and the primary action is front-loaded with the negative constraint as a tight follow-up. Every clause earns its place.

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

Completeness3/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 no explanation, and the annotations carry the safety profile. Still, for a creation tool with a type-dependent nested reference object and idempotentHint=false, the description omits duplicate/already-registered behavior and any hint about required fields per storage type.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Top-level schema description coverage is 0% for 'name' and 'reference', and the description adds no parameter meaning at all — it never explains the nested reference object, the 'type' discriminator, or which fields each storage type requires. The nested property descriptions carry that load, but the description itself does nothing to compensate for the coverage gap.

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 ('Register an existing bucket, container, or directory') and immediately bounds the scope with 'Does not create cloud resources', which cleanly separates it from a provisioning tool. It does not name a sibling such as create_storage_subscription or list_storage_locations to sharpen the distinction, so it stops short of a 5.

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 'existing' plus 'Does not create cloud resources' implies the precondition that the bucket/container/directory must already exist, which is genuine implied usage guidance. However there is no explicit when-to-use vs. alternative statement, no note on what to do for a not-yet-existing resource, and no prerequisites for credentials or permissions.

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

All Tilebox 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