Scribase

Create a storage bucket

storage.buckets.create

Create a storage bucket. Private by default; public: true makes objects readable by URL. Scope: storage:write.

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": "storage.buckets.create"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Bucket name
`branch`	No	Branch (environment) id. Optional: defaults to `production`.
`public`	No	Publicly readable (default false)
`project_id`	No	Project id. Optional: defaults to the project created or used last in this session, or the only one.
`file_size_limit`	No	Maximum object size in bytes
`organization_id`	No	Organization id. Optional: defaults to the token's organization, or the only one you belong to.
`allowed_mime_types`	No	Allowed MIME types, e.g. ["image/png", "image/*"]

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world write. The description adds genuinely new behavior: the bucket is private by default, the public flag exposes objects via URL, and it requires the storage:write scope. It omits duplicate-name/error behavior, which is the one meaningful gap.

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?

Three short, front-loaded clauses cover the action, the most consequential default, and the auth requirement with no filler. Every sentence carries information an agent needs.

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 seven-parameter creation tool with full schema coverage, existing annotations, and no output schema, the description covers the essentials an agent needs to invoke it correctly. It would be complete at a 5 if it stated what happens when a bucket with the same name already exists.

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 100%, so the schema already documents all seven parameters including defaults for branch, project_id, and organization_id. The description's note that public: true makes objects readable by URL adds only slight meaning beyond the schema's "Publicly readable (default false)", so the baseline of 3 applies.

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 description opens with a specific verb+resource pair ("Create a storage bucket") that unambiguously separates it from the sibling read tools storage.buckets and storage.buckets.list. It does not name those siblings explicitly, so it stops just 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?

Usage context is only implied: the agent learns the operation creates something and that privacy is the default. There is no explicit when-to-use/when-not, no mention of prerequisites beyond the write scope, and no routing away from the list siblings.

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

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