Skip to main content
Glama
collapseindex

CI-1T Prediction Stability Engine

fleet_session_state

Inspect accumulated fleet session results between rounds. Retrieve session state, round count, node details, and fleet summary without submitting new scores.

Instructions

Get the current state of a fleet session without submitting new scores. Response: { session_id, round_count, nodes: [{ node_id, node_name, episodes: [...] }], fleet_summary }. Use to inspect accumulated results between rounds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYesFleet session ID

Implementation Reference

  • src/index.ts:651-667 (registration)
    Registration of the 'fleet_session_state' tool via server.tool(), with its Zod schema input definition (session_id) and handler.
    server.tool(
      "fleet_session_state",
      "Get the current state of a fleet session without submitting new scores. Response: { session_id, round_count, nodes: [{ node_id, node_name, episodes: [...] }], fleet_summary }. Use to inspect accumulated results between rounds.",
      {
        session_id: z.string().describe("Fleet session ID"),
      },
      async ({ session_id }) => {
        const guard = requireApiKey();
        if (guard) return guard;
        const result = await apiFetch("/api/fleet-session", {
          method: "POST",
          headers: apiKeyHeaders(),
          body: { action: "state", session_id },
        });
        return formatResult(result);
      }
    );
  • Zod schema defining the input: session_id (string) is the only required parameter.
    {
      session_id: z.string().describe("Fleet session ID"),
    },
  • Handler function that checks for API key, then calls POST /api/fleet-session with action:'state' and session_id to fetch current fleet session state.
    async ({ session_id }) => {
      const guard = requireApiKey();
      if (guard) return guard;
      const result = await apiFetch("/api/fleet-session", {
        method: "POST",
        headers: apiKeyHeaders(),
        body: { action: "state", session_id },
      });
      return formatResult(result);
    }
Behavior3/5

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

No annotations provided, so description must carry behavioral disclosure. It explains the read-only nature and response structure, but omits details like error handling or prerequisites.

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?

Two concise, front-loaded sentences with no superfluous information, efficiently conveying purpose and usage.

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?

Adequately covers purpose, usage, and response format for a simple tool, though it could be improved by mentioning potential error states or prerequisites.

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?

With 100% schema coverage, the description adds no additional semantic value beyond what the schema already offers for the single parameter.

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 action ('get') and resource ('current state of a fleet session'), and distinguishes it from sibling tools like fleet_session_create or fleet_session_list.

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

Usage Guidelines4/5

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

Explicitly advises using it to inspect accumulated results between rounds, providing clear context but lacking explicit when-not-to-use or alternative pointers.

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

Install Server

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/collapseindex/ci-1t-mcp'

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