tela

by zcag

Overview Schema Source Related Servers Discussions Admin

Remote

Update space

update_space

Idempotent

Patch a space's name or slug to update its display or URL path. Idempotent: only pass the fields you want to change.

Instructions

Patch a space's name and/or slug (editor+); idempotent — pass only the field(s) you want to change. Changing the slug updates the space's URL path (existing page ids and links still resolve). To create a space use create_space, to read it use get_space, to remove it use delete_space.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	space id to patch
`name`	No	new name (omit to leave unchanged)
`slug`	No	new slug (omit to leave unchanged)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`space`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations provide idempotentHint=true, destructiveHint=false. Description adds that changing slug updates URL path while existing IDs still resolve—useful context beyond annotations. No contradictions.

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 precise sentences front-load the action, idempotency, and field selection guidance. No wasted words.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With output schema present, description needn't detail returns. It covers purpose, usage, and side effects (URL update) adequately for a patch operation.

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 coverage is 100% with clear parameter descriptions. Description reinforces 'pass only fields to change' but doesn't add significant new info beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool patches a space's name and/or slug (specific verb+resource+fields). It also distinguishes from sibling tools by referencing create_space, get_space, and delete_space.

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

Usage Guidelines5/5

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

Explicitly tells when to use this tool (to update name/slug) and when not to (use create_space, get_space, delete_space for other operations). Also notes idempotency and to pass only changed fields.

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