Skip to main content
Glama

Get or create agent

create_agent
Idempotent

Get or create a persistent cloud agent to accumulate project files, tools, and long-running jobs. Reusing a name reconnects to your existing agent.

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 plan limits (agent count, model tier); model is ignored when an existing agent is returned (use set_agent_model to change it).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe agent's name. Reusing a previous name returns that existing agent.
modelNoOptional 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.
Install Server

TDQS

A5/5.0
Behavior5/5

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

Beyond the annotations (idempotentHint), the description discloses idempotent behavior (returns existing agent if name exists) and notes that the model parameter is ignored when reusing an existing agent. It also mentions account plan limits for creation, adding significant behavioral context not present in annotations.

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?

The description is concise yet comprehensive, with each sentence serving a purpose. It covers purpose, usage context, idempotency, and limitations without redundancy, maintaining clear logical flow.

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?

Given only two parameters and no output schema, the description covers all essential aspects: core function, illustrative use cases, anti-cases, behavior on reconnection, and plan constraints. It is fully self-contained for an agent to decide and invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema already describes both parameters, the description adds crucial nuances: for 'model', it explains the default routing behavior (cheapest fitting model) and the paid-plan requirement for frontier models. This enriches the schema and clarifies practical usage.

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's purpose as 'Get or create an agent by name' and distinguishes it from sibling get_agent/list_agents by emphasizing the create-or-reuse behavior. It explicitly mentions persistent environment and the right way to reconnect, making it unambiguous.

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 guidance on when to use (long-term projects, accumulating files) and when not to use (one-off scripts), plus highlights it as the correct method for reconnecting to an existing agent. This fully equips an agent to choose this tool appropriately over alternatives.

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

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/plori-ai/plori'

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