Plori

Official

by plori-ai

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Get agent details

get_agent

Read-only

Retrieve an agent's details and mailbox by UUID. Returns name, type, model, status, plus up to 20 messages, with open letters first and newest within each group.

Instructions

Get one agent's details (name, type, model, status) by its id, and its mailbox: same-account mail from other agents, open letters first (accepted, delivering, blocked), then applied or undeliverable ones, newest within each group, capped at 20.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`agent_id`	Yes	The agent's UUID (from list_agents or create_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.
`mailbox`	Yes	This agent's mailbox letters, open ones (accepted, delivering, blocked) first, then applied or undeliverable ones, newest within each group, at most 20.
`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.
`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",
-  "mailbox"
-]New value: +[
+  "id",
+  "user_id",
+  "name",
+  "backend",
+  "model",
+  "advisor_max_spend_micro_usd",
+  "effective_model",
+  "config",
+  "created_at",
+  "mailbox"
+]

Changed1 schema field changedv0.16.0Sep 19, 2026

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"
+    },
+    "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"
+      ]
+    },
+    "mailbox": {
+      "description": "This agent's mailbox letters, open ones (accepted, delivering, blocked) first, then applied or undeliverable ones, newest within each group, at most 20.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "accepted_at": {
+            "type": "string"
+          },
+          "block_reason": {
+            "type": "string"
+          },
+          "consumed_at": {
+            "type": [
+              "null",
+              "string"
+            ]
+          },
+          "correlation_id": {
+            "type": "string"
+          },
+          "from_agent": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "in_reply_to": {
+            "type": [
+              "null",
+              "string"
+            ]
+          },
+          "kind": {
+            "type": "string"
+          },
+          "run_id": {
+            "type": [
+              "null",
+              "string"
+            ]
+          },
+          "status": {
+            "type": "string"
+          },
+          "summary": {
+            "type": "string"
+          },
+          "to_agent": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "kind",
+          "from_agent",
+          "to_agent",
+          "status",
+          "in_reply_to",
+          "correlation_id",
+          "run_id",
+          "summary",
+          "accepted_at",
+          "consumed_at"
+        ],
+        "type": "object"
+      },
+      "type": [
+        "null",
+        "array"
+      ]
+    },
+    "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",
+    "mailbox"
+  ],
+  "type": "object"
+}

Addedv0.7.0Aug 9, 2026
Removedv0.3.0Jul 26, 2026
First observedv0.1.0Jul 4, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered, and the description still adds substantive behavioral context: the mailbox is scoped to same-account mail from other agents, is ordered (open letters first by status group, newest within group), and is capped at 20. That ordering and truncation disclosure is genuinely useful beyond the 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?

A single dense sentence with the primary purpose front-loaded and the mailbox caveats trailing. Every clause adds information (fields, ordering, cap), though the mailbox clause makes it longer than strictly needed for a getter.

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?

An output schema exists, so return-value documentation is not required, yet the description still characterizes the mailbox payload and its limit. With the single parameter fully documented in the schema, an agent has everything needed to call this correctly; only explicit sibling routing is 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?

There is only one parameter and schema description coverage is 100% ('The agent's UUID (from list_agents or create_agent)'), so the schema already carries the full meaning. The description adds only the phrase 'by its id', so baseline 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?

States a specific verb ('Get') and resource ('one agent's details') and enumerates exactly which fields are returned (name, type, model, status) plus the mailbox payload. The singular 'one agent ... by its id' implicitly but clearly separates it from the sibling list_agents.

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

Usage Guidelines3/5

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

The retrieval scope is clear enough to imply when to call it (you have an agent id and want that agent), but there is no explicit when-to-use/when-not guidance and no named alternative such as list_agents or get_run_result. Usage is inferred rather than directed.

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