Plori

Official

by plori-ai

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Get or create agent

create_agent

Idempotent

Create or reconnect to a persistent cloud agent environment by name, with its own disk, tools, and memory. Use it to accumulate project files, keep repos checked out, or hand off long-running jobs.

Instructions

Get or create an agent by name: a persistent cloud environment running plori's agent, with its own disk, tools, and memory. Create one when the work should accumulate somewhere the user can return to: a project with files that build up, a repo to keep checked out, tools to install once and reuse, or a long job to hand off. You do not need one for a question you can answer yourself or for a one-off script with no state worth keeping. If the account already has an agent with this name, that agent is returned (marked "existing": true) instead of a duplicate — safe to call repeatedly, and the right way to reconnect to an agent you used before. Creation is subject to the account's agent-count limit. The Plori Router chooses the model for each task.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	The agent's name. Reusing a previous name returns that existing agent.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	The Agent's unique identifier; pass it to other tools as agent_id.
`url`	No	This Agent's page in the plori web app.
`name`	Yes	The Agent's name, chosen by its owner and unique within the account.
`model`	Yes	The model slug this Agent is configured to use. Empty means no explicit choice, which is not the same as no model — read effective_model for what a run will actually use.
`config`	Yes	Arbitrary JSON owned by the producing engine.
`moving`	No	True while this Agent's files are being copied to a new disk; check storage_notice rather than a separate route for the outcome.
`status`	No	The live warm-session state: warming, ready, or sleeping; empty when no session is active.
`backend`	Yes	The compute backend this Agent runs on.
`user_id`	Yes	The identifier of the account that owns this Agent.
`deleting`	No	True while this Agent's disk is still being erased; offer no action on it besides retrying the deletion itself.
`existing`	No	Whether create_agent returned an existing same-name agent instead of creating one.
`queued_at`	No	When a still-warming attach was accepted; present only while it is queued for node capacity.
`created_at`	Yes	When the Agent was created.
`last_run_at`	No	When this Agent last started a run; absent when it has never run.
`deleting_since`	No	When the deletion was first requested; present only while deleting is true.
`storage_notice`	No	The one sentence, if any, telling the owner about a storage move that stopped; show it verbatim, not paraphrased.
`effective_model`	Yes	The model a run on this Agent will actually use. plori-auto means the hosted router chooses per turn.
`advisor_max_spend_micro_usd`	Yes	Optional maximum advisor-completion spend per turn in micro-US-dollars. Zero disables advisor completions; null leaves no spend cap.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.16.2Sep 21, 2026

addedOutput schema / properties / advisor_max_spend_micro_usd

Added value: +{
+  "description": "Optional maximum advisor-completion spend per turn in micro-US-dollars. Zero disables advisor completions; null leaves no spend cap.",
+  "type": [
+    "null",
+    "integer"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "id",
-  "user_id",
-  "name",
-  "backend",
-  "model",
-  "effective_model",
-  "config",
-  "created_at"
-]New value: +[
+  "id",
+  "user_id",
+  "name",
+  "backend",
+  "model",
+  "advisor_max_spend_micro_usd",
+  "effective_model",
+  "config",
+  "created_at"
+]

Changed2 schema fields changedv0.16.0Sep 19, 2026

removedInput schema / properties / model

Removed value: -{
-  "description": "Optional model slug; omitted uses the Plori Router, which picks the cheapest model that fits each task from the pool the account's plan unlocks. An explicit frontier model still requires a paid plan.",
-  "type": "string"
-}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "backend": {
+      "description": "The compute backend this Agent runs on.",
+      "type": "string"
+    },
+    "config": {
+      "description": "Arbitrary JSON owned by the producing engine."
+    },
+    "created_at": {
+      "description": "When the Agent was created.",
+      "type": "string"
+    },
+    "deleting": {
+      "description": "True while this Agent's disk is still being erased; offer no action on it besides retrying the deletion itself.",
+      "type": "boolean"
+    },
+    "deleting_since": {
+      "description": "When the deletion was first requested; present only while deleting is true.",
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "effective_model": {
+      "description": "The model a run on this Agent will actually use. plori-auto means the hosted router chooses per turn.",
+      "type": "string"
+    },
+    "existing": {
+      "description": "Whether create_agent returned an existing same-name agent instead of creating one.",
+      "type": "boolean"
+    },
+    "id": {
+      "description": "The Agent's unique identifier; pass it to other tools as agent_id.",
+      "type": "string"
+    },
+    "last_run_at": {
+      "description": "When this Agent last started a run; absent when it has never run.",
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "model": {
+      "description": "The model slug this Agent is configured to use. Empty means no explicit choice, which is not the same as no model — read effective_model for what a run will actually use.",
+      "type": "string"
+    },
+    "moving": {
+      "description": "True while this Agent's files are being copied to a new disk; check storage_notice rather than a separate route for the outcome.",
+      "type": "boolean"
+    },
+    "name": {
+      "description": "The Agent's name, chosen by its owner and unique within the account.",
+      "type": "string"
+    },
+    "queued_at": {
+      "description": "When a still-warming attach was accepted; present only while it is queued for node capacity.",
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "status": {
+      "description": "The live warm-session state: warming, ready, or sleeping; empty when no session is active.",
+      "type": "string"
+    },
+    "storage_notice": {
+      "description": "The one sentence, if any, telling the owner about a storage move that stopped; show it verbatim, not paraphrased.",
+      "type": "string"
+    },
+    "url": {
+      "description": "This Agent's page in the plori web app.",
+      "type": "string"
+    },
+    "user_id": {
+      "description": "The identifier of the account that owns this Agent.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "user_id",
+    "name",
+    "backend",
+    "model",
+    "effective_model",
+    "config",
+    "created_at"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv0.7.0Aug 9, 2026

changedInput schema / properties / model / description

Previous value: -"Optional model slug; omitted uses Auto, the plan-scaled default whose quality follows the account's plan. An explicit frontier model requires a paid plan."New value: +"Optional model slug; omitted uses the Plori Router, which picks the cheapest model that fits each task from the pool the account's plan unlocks. An explicit frontier model still requires a paid plan."

Changed1 schema field changedv0.3.0Jul 26, 2026

changedInput schema / properties / model / description

Previous value: -"Optional model slug; omitted uses the account's tier default. Frontier models require a paid plan."New value: +"Optional model slug; omitted uses Auto, the plan-scaled default whose quality follows the account's plan. An explicit frontier model requires a paid plan."

Changed1 schema field changedv0.1.1Jul 16, 2026

changedInput schema / properties / name / description

Previous value: -"A human-readable name for the agent."New value: +"The agent's name. Reusing a previous name returns that existing agent."

First observedv0.1.0Jul 4, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already indicate idempotentHint=true and destructiveHint=false. The description adds valuable behavioral context: returned agents are marked 'existing', safe repeated calls, account-level agent-count limits, and the Plori Router choosing the model. No contradiction with annotations.

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?

The description is front-loaded with the core purpose and then expands logically into use cases, idempotency, limits, and routing. It is longer than minimal, but each section earns its place. Minor redundancy exists because 'safe to call repeatedly' partly repeats the idempotentHint annotation.

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?

The description is complete for a create-or-get tool: it explains the resource, when to use it, idempotency, account limits, and model selection. The output schema exists, so return values need not be described in the text. No critical operational detail appears missing.

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 the schema fully documents the name parameter and its reuse behavior. The description reiterates that reusing a name returns the existing agent but does not add materially new parameter-level detail, so the baseline of 3 applies.

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 clearly states that the tool gets or creates an agent by name, and defines the agent as a persistent cloud environment with its own disk, tools, and memory. It differentiates from siblings by emphasizing reuse semantics ('If the account already has an agent with this name, that agent is returned'), though it does not explicitly name alternatives like get_agent or invoke_agent.

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?

The description provides explicit when-to-use guidance: persistent projects, checked-out repos, reusable tools, and long hand-off jobs. It also states when not to use it: simple questions or one-off scripts with no state worth keeping. This is strong, actionable guidance.

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