Skip to main content
Glama

面灵AI 面试助手

list_exams

Read-only

列出用户的笔试记录(桌面客户端截屏答题的场次),每行一场,最近有更新的在前,每页 20 场。(需要用户授权,范围 interviews:read)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_exams"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real value beyond them: result ordering (most recently updated first), page size (20 records per page), one record per line, and the required auth scope. What it omits is the shape of each row and whether more pages exist beyond the schema's max of 100.

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?

A single compact sentence with the resource, ordering, page size, and auth scope front-loaded; the parentheticals carry genuine disambiguating content rather than filler. Nothing is redundant.

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?

For a simple, read-only, single-parameter list tool with no output schema, the description covers what is returned (one exam session per line), how it is ordered, how much per page, and the auth requirement. Minor gaps are the row field contents and end-of-pagination behavior.

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 single 'page' parameter has no description in the schema, but the schema does supply default=1, min=1, and max=100. The description compensates partially by revealing the 20-records-per-page size, letting an agent derive offsets, but it never explains what 'page' selects or what happens when it exceeds the last page.

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 gives an explicit verb/resource pair ('列出用户的笔试记录') and adds a clarifying parenthetical defining what an exam record is (sessions answered by screenshot in the desktop client), which meaningfully separates it from interview-list siblings. It stops short of naming any alternative tool, so the differentiation is inferential rather than stated.

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 context is only implied by the resource definition; there is no explicit statement of when to call this versus list_interviews or list_my_interview_experiences. The authorization prerequisite (interviews:read) is a useful call-time condition, but no exclusions or alternatives are offered.

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.

Resources