Create a new dataspace in Locus to organize local semantic content. Use it as a dedicated container for ingesting documents and running semantic searches.
Create a new dataspace in Locus
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Name of the dataspace to create |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry behavioral disclosure, but it only restates the create action. It does not mention idempotency, duplicate-name behavior, or whether creation is irreversible; this is a meaningful transparency gap for a mutation tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler; the action and target resource are stated in the fewest words that retain meaning.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter creation tool with no output schema, the description is minimally viable, but an agent still lacks information about success/failure behavior, duplicate handling, or side effects. This is a clear gap without being severe.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already documents the single name parameter with 100% coverage, so the baseline is 3. The description adds no additional semantic detail about name format or constraints, but it doesn't need to compensate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb (Create) and resource (dataspace, in Locus), clealy distinguishing this tool from list_spaces/delete_space and from docment/scpace tools. An agent can identify the intended operation without needing extra context.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is for creating a new dataspace, which is the only place such an operation could occur among the siblings, but it does not explicitly state when to use it over alternatives or any exclusions. This is adequate but minimal.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.