Skip to main content
Glama
Sign In

Scribase

by com.scribase
OverviewDiscussionsAdmin

org.put

Create or update an organization. PUT /v1/organizations/{id}.

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": {
      "organization_id": "<organization_id>",
      "display_name": "<display_name>",
      "confirm": "<confirm>"
    },
    "name": "org.put"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true to apply this mutation; otherwise the tool returns the request it would send for approval.
display_nameYesdisplay_name (required)
organization_idYesorganization_id (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/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 mutation, so the description adds nothing on the safety axis. The most important behavioral trait — the 'confirm' gate that returns the request for approval instead of applying it — is documented only in the schema, not the description. The PUT endpoint reference is metadata rather than behavior.

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?

Two short sentences, front-loaded with the action and resource, with zero filler. The trailing endpoint path is mildly redundant but does help map the call to the underlying API reference.

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?

For a mutation tool the annotations and fully documented schema cover most of what an agent needs, including the unusual confirm-based dry-run flow. The description itself leaves the create-vs-update semantics unexplained and does not warn that the call is a no-op unless confirm is true.

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 all three parameters including the confirm approval gate are already documented in structured data. The description adds no meaning beyond that, which is the expected baseline when the schema carries the burden.

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 states a specific verb pair and resource ('Create or update an organization'), which cleanly separates it from read siblings like org.get and org.list. It is slightly ambiguous because organization_id is required, so the 'create' branch is never explained, and no sibling such as project.put or member.put is named for contrast.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: nothing tells the agent when to call this versus org.get, org.list, or org.put's counterpart mutation tools. Nothing explains the create-vs-update precondition or what state the organization must be in.

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

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