Skip to main content
Glama

roiq_create_space

Create a new space for a team, client, or private use. The space is initially visible only to Owner/Admin until assigned in Configurations.

Instructions

Crea un espacio nuevo (equipo, cliente o privado). Nace sin teams asignados → sólo Owner/Admin lo ven hasta asignarlo en Configuraciones.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
iconNoicono, ej. 'svg:building' o un emoji
kindNoteam (equipo, por defecto) | client | private
nameYesnombre del espacio
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses that the space is initially visible only to Owner/Admin until assigned in Configuraciones, which is useful behavioral context beyond the schema.

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 concise sentences with front-loaded main action and essential behavioral detail. No unnecessary words.

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 simple creation tool with 3 parameters and no output schema, the description covers purpose and key behavioral trait. Could mention return value or error conditions, but not critical.

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 descriptions for all parameters. The description adds no additional parameter information; baseline score of 3 is appropriate.

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?

Description uses specific verb 'Crea' and resource 'espacio nuevo' with three types (equipo, cliente, privado). It clearly distinguishes from sibling tools like roiq_list_spaces or roiq_create_db.

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

Usage Guidelines4/5

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

States the tool is for creating a new space and provides post-creation behavior context. Does not explicitly mention when not to use or alternatives, but the purpose is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/crisglezz/roiq-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server