Skip to main content
Glama

Export state

export_state
Read-onlyIdempotent

Portable state document for an agent (import_state recreates it anywhere — including a self-hosted verdigraph-neurogenesis).

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": {
      "agent_id": "<agent_id>"
    },
    "name": "export_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesThe developmental agent's id, from create_agent.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / agent_id / description
      Added value: +"The developmental agent's id, from create_agent."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds genuine behavioral context the annotations lack: the output is a portable document and import_state can reconstitute it anywhere, including self-hosted deployments. It stops short of noting what is captured, whether secrets are included, or size/transfer constraints.

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?

One tight sentence with the resource ('portable state document') front-loaded and the round-trip use case parenthetically appended. Nothing superfluous, though the parenthetical deployment example is slightly promotional rather than operational.

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 values needn't be described, and annotations plus the schema cover safety and the single parameter. The description supplies the round-trip context (import_state) that makes the tool's role unambiguous. What remains missing is minor: any indication of export scope or limitations.

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 a single required parameter with 100% schema description coverage ('The developmental agent's id, from create_agent'), so the schema already carries the semantics. The description adds nothing about agent_id, which is acceptable at this coverage level but not credit-earning.

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 frames the tool as producing a 'portable state document for an agent,' which is a clear resource and outcome, and it names the inverse sibling import_state so the agent can distinguish the pair. The explicit verb 'export' lives in the name/title rather than the description, which keeps it just short of a 5.

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?

It implies the use case (snapshot an agent so import_state can recreate it elsewhere, including a self-hosted verdigraph-neurogenesis) but never states when to export versus when another tool is appropriate, nor any exclusions or prerequisites such as agent state requirements before export.

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.