Skip to main content
Glama
Sign In
Learn Shell

Learn Shell

by sf-shenfeng
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_exercise

Retrieve an exercise's prompt, reference answer, expected concepts, tags, and lesson info for grading preparation. Returns NOT_FOUND for exercises outside the current pair.

Instructions

读回一道习题: prompt / reference_answer / expected_concepts / tags / 所属 lesson (lesson_id + lesson_title + course_id)。批改前先审教材用这个取题面与评分标准。reference_answer 是评分钥匙 (教师侧机密) — 不要原样透给学习者。只能读当前 pair 的题, 其他 pair (或不存在) 的 exercise_id 一律 NOT_FOUND。

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": {
      "exercise_id": "<exercise_id>"
    },
    "name": "get_exercise"
  }
}

Input Schema

NameRequiredDescriptionDefault
exercise_idYes必填; 要读回的 exercise id (ex_ 前缀), 须属当前 pair

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and delivers. It discloses that reference_answer is the confidential grading key and instructs not to leak it to learners, and that only exercises in the current pair can be read, with other/nonexistent IDs returning NOT_FOUND. These are meaningful behavioral details beyond a basic 'get'.

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 one compound sentence but densely packs purpose, return fields, usage context, confidentiality warning, and scope constraint. It is front-loaded with the core purpose and contains no filler, though the structure is somewhat run-on.

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

Completeness5/5

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

Given the lack of output schema and annotations, the description provides a thorough picture: return fields are enumerated, error behavior (NOT_FOUND) is specified, and the confidentiality warning covers an important handling concern. For a simple read tool, this is fully complete.

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% and the parameter description already explains the ex_ prefix and the current-pair requirement. The tool description mostly restates this constraint and adds no new parameter-level meaning, so it remains at the baseline.

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 uses a specific verb ('读回'/'read back') with the resource 'exercise' and explicitly lists the returned fields (prompt, reference_answer, expected_concepts, tags, lesson info). This clearly differentiates it from siblings like add_exercise (creating) and grade_exercise (grading).

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?

It explicitly states when to use: '批改前先审教材用这个' (use this to fetch the problem statement and grading criteria before grading). It provides clear context, though it does not explicitly name alternatives or exclusions.

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

Deploy Server

Other Tools