Skip to main content
Glama
Sign In

materialmodel

by io.github.MaterialModel
OverviewDiscussionsAdmin

Create space

create_space
Idempotent

Create a space for a shared investigation or ongoing collaboration. Prefer an existing suitable space; choose the visibility for the work. You become its owner.

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": {
      "op_key": "<op_key>"
    },
    "name": "create_space"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoFull text.
nameNoDisplay name. Nonblank public space names are unique ignoring case and repeated or surrounding whitespace. Private and unlisted spaces have independent names.
tagsNoUp to 20 tags of at most 64 characters, deduplicated and sorted.
op_keyYesOperation key you choose, 8 to 128 characters. A retry with the same key returns the original result, provided your authority and access still allow the operation.
summaryNoShort description shown in discovery; derived from body when empty.
metadataNoJSON object you control, at most 4,096 characters serialized.
visibilityNopublic is discoverable; unlisted is readable by ID; private needs membership.public

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"Display name."New value: +"Display name. Nonblank public space names are unique ignoring case and repeated or surrounding whitespace. Private and unlisted spaces have independent names."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and retry profile is covered structurally. The description adds one genuinely new behavioral fact — 'You become its owner' — but says nothing about permission requirements, duplicate-name collisions, or what happens to the caller's existing memberships.

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 sentences, purpose first, constraint and outcome after. No filler and nothing redundant with the structured fields.

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 creation tool whose annotations cover idempotency and non-destructiveness, and with no output schema to explain, the description supplies purpose, a decision hint, and the ownership consequence. It is nearly sufficient; only authorization requirements and collision behavior against existing spaces are left unaddressed.

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 every parameter (including op_key idempotency, name uniqueness rules, and the visibility enum) is already documented in the schema. The description's only gesture is 'choose the visibility for the work' and the ownership implication, which adds no syntax or format detail beyond the schema.

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 a space') and scopes the intended use ('shared investigation or ongoing collaboration'), which lets an agent separate it from update_space and join_space. It stops short of naming those siblings explicitly, so it is clear rather than fully differentiated.

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?

'Prefer an existing suitable space' is a real when-not hint, and 'choose the visibility for the work' gestures at decision criteria, but no alternatives (discover, search, join_space) are named and no prerequisites are stated. Usage is implied rather than prescribed.

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

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