Skip to main content
Glama

mavis_session_info

Get detailed session info including status, workspace, and model. Provide a session ID to retrieve current session data.

Instructions

Get detailed info about a specific session (status, workspace, model, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesSession ID (e.g. mvs_xxx)

Implementation Reference

  • src/index.js:119-126 (registration)
    Tool definition and registration for 'mavis_session_info' in the tools array. It specifies the name, description, inputSchema (zod schema requiring a sessionId string), and buildArgs function that constructs CLI args ['session', 'info', sessionId] for the Mavis CLI.
    {
      name: 'mavis_session_info',
      description: 'Get detailed info about a specific session (status, workspace, model, etc.)',
      inputSchema: z.object({
        sessionId: z.string().describe('Session ID (e.g. mvs_xxx)')
      }),
      buildArgs: ({ sessionId }) => ['session', 'info', sessionId]
    },
  • Input schema for mavis_session_info defined using Zod. Requires a single parameter 'sessionId' (string) with description 'Session ID (e.g. mvs_xxx)'.
    inputSchema: z.object({
      sessionId: z.string().describe('Session ID (e.g. mvs_xxx)')
    }),
  • The buildArgs handler function that translates parsed arguments into CLI command ['session', 'info', sessionId] to be executed via execMavisJSON (the default exec path since no execFn is specified).
      buildArgs: ({ sessionId }) => ['session', 'info', sessionId]
    },
  • The execMavisJSON helper function that the tool uses to call the Mavis CLI and parse JSON output. Since mavis_session_info does not specify execFn, it defaults to this JSON-based execution path.
    function execMavisJSON(args) {
      return execMavis(args).then(raw => {
        try {
          return JSON.parse(raw);
        } catch {
          const jsonStart = raw.indexOf('{');
          return JSON.parse(jsonStart >= 0 ? raw.slice(jsonStart) : raw);
        }
      });
    }
  • Test data sample for mavis_session_info used in schema validation tests: { sessionId: 'mvs_test123' }.
    mavis_session_info: { sessionId: 'mvs_test123' },
Behavior3/5

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

No annotations provided, so description carries the burden. It implies a read-only operation, but no explicit mention of side effects, permissions, or rate limits. Adequate for a simple get operation but lacks depth.

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?

Single sentence, front-loaded with key purpose, no wasted words. Excellent conciseness.

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

Completeness3/5

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

No output schema, so description should detail return fields. It lists only 'status, workspace, model, etc.' which is vague. Missing explicit mention of whether response includes timestamps, metadata, or error handling.

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% with a single parameter 'sessionId' described. The description adds no additional meaning beyond the schema, which already includes a format example. Baseline 3 applies.

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 clearly states 'Get detailed info about a specific session' with examples of returned fields. It distinguishes it from list and create tools, but doesn't fully differentiate from other session detail tools like mavis_session_messages.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like mavis_session_list or mavis_session_messages. The description does not provide context or exclusion criteria.

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/Cunning-Kang/mavis-mcp-server'

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