Skip to main content
Glama

Import state

import_state

Recreate an agent from an export_state document.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "state": "<state>"
    },
    "name": "import_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesA document from export_state, unchanged.
request_idNoOptional. Your id for this call. Repeat it to retry safely: the same request_id is never charged twice.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / request_id / description
      Added value: +"Optional. Your id for this call. Repeat it to retry safely: the same request_id is never charged twice."
    • addedInput schema / properties / state / description
      Added value: +"A document from export_state, unchanged."
  2. First observed

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, so the safety profile is carried for it, but the description adds nothing beyond that. It is unclear whether import creates a new agent or overwrites an existing one, whether identifiers are preserved, or what permissions the call needs — material facts for a provisioning operation, especially given idempotentHint=false.

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 front-loaded sentence with no filler or redundancy. Its brevity is efficient rather than padded, though that same economy leaves the substance thin.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Only one sentence for a non-idempotent mutation that provisions an agent from a nested state document. The output schema handles return values, but the description should still state whether an existing agent is replaced, whether the import is charged/creatable multiple times, and any auth or size constraints.

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%, so baseline 3 applies; both `state` and `request_id` are documented in the schema, including the retry-safety semantics of request_id. The description does not add any meaning on top of the schema (it restates the 'from export_state' constraint already present in the state property description).

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?

States a specific verb and resource ('Recreate an agent') and names its source sibling ('from an export_state document'), so an agent can distinguish it from export_state. It stops short of full sibling differentiation — nothing is said about create_agent or import's relationship to list_agents/describe_agent.

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?

Usage is only implied: the reader infers 'use this when you hold an export_state document and want the agent back.' There is no explicit when-to-use framing versus create_agent, no prerequisites, and no statement about what to do if the agent already exists.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.