Skip to main content
Glama

get_progress

Check current MBTI test progress by providing session state, showing answered questions and remaining items in personality assessment.

Instructions

查询当前测试进度。需要传入测试会话状态。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionYes测试会话状态

Implementation Reference

  • src/index.ts:78-97 (registration)
    Registration of the 'get_progress' tool in the ListTools handler, defining its name, description, and input schema.
    {
      name: 'get_progress',
      description: '查询当前测试进度。需要传入测试会话状态。',
      inputSchema: {
        type: 'object',
        properties: {
          session: {
            type: 'object',
            description: '测试会话状态',
            properties: {
              testType: { type: 'string' },
              answers: { type: 'array' },
              currentQuestionIndex: { type: 'number' },
            },
            required: ['testType', 'answers', 'currentQuestionIndex'],
          },
        },
        required: ['session'],
      },
    },
  • Input schema for the 'get_progress' tool, validating the session object.
    inputSchema: {
      type: 'object',
      properties: {
        session: {
          type: 'object',
          description: '测试会话状态',
          properties: {
            testType: { type: 'string' },
            answers: { type: 'array' },
            currentQuestionIndex: { type: 'number' },
          },
          required: ['testType', 'answers', 'currentQuestionIndex'],
        },
      },
      required: ['session'],
    },
  • Handler implementation for the 'get_progress' tool. Computes progress percentage and completion status based on the provided session state and question bank total.
    if (name === 'get_progress') {
      const session = args.session as TestSession;
      const questions = session.testType === 'simplified'
        ? questionBank.simplified
        : questionBank.cognitive;
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify({
              testType: session.testType,
              progress: {
                answered: session.answers.length,
                total: questions.length,
                percentage: Math.round((session.answers.length / questions.length) * 100),
              },
              completed: session.answers.length >= questions.length,
            }, null, 2),
          },
        ],
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the tool queries progress and requires session input, without describing what 'progress' means (e.g., percentage, status, next steps), whether it's read-only (implied but not explicit), what happens if the session is invalid, or any error conditions. For a tool with no annotations, this leaves significant behavioral gaps.

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?

The description is appropriately concise with two short sentences that state the purpose and parameter requirement without unnecessary details. It's front-loaded with the main function. However, it could be slightly more structured by explicitly separating purpose from requirements, but it remains efficient with zero waste.

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?

Given the complexity (1 parameter with nested object, no output schema, no annotations), the description is incomplete. It doesn't explain what 'progress' entails (e.g., a percentage, status message, or structured data), how the session properties influence the output, or any error handling. Without annotations or output schema, the description should provide more context about the tool's behavior and results, but it falls short.

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?

The description adds minimal value beyond the input schema, which has 100% coverage. It mentions that a test session state is required, aligning with the schema's 'session' parameter description ('测试会话状态'). However, it doesn't explain what 'progress' means in relation to the session properties (testType, answers, currentQuestionIndex) or how these affect the query. With high schema coverage, the baseline is 3, and the description doesn't significantly enhance parameter understanding.

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 the tool's purpose as '查询当前测试进度' (query current test progress), which is a specific verb+resource combination. It distinguishes itself from siblings like 'start_mbti_test' (initiation) and 'calculate_mbti_result' (final calculation), though it doesn't explicitly differentiate from 'answer_question' which might be related but serves a different function. The purpose is clear but lacks explicit sibling differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives. It mentions that a test session state is required ('需要传入测试会话状态'), but this is more of a parameter requirement than usage context. There's no indication of when this tool should be called during a test flow, what prerequisites exist, or how it relates to sibling tools like 'answer_question' or 'calculate_mbti_result'.

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/wenyili/mbti-mcp'

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