Skip to main content
Glama

query_group_snapshot

Retrieve a comprehensive snapshot of a course group, including assignments and attendance statistics, by providing the group ID.

Instructions

查询课程组总览快照

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idYes课程组id(通过 query_teacher_groups 获取)
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'query', implying a read operation, but lacks details such as what the snapshot contains, whether it's idempotent, or any other behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise (a single phrase), but it sacrifices informativeness for brevity. While it is not verbose, it lacks structure and could benefit from additional context.

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 tool has no output schema, the description should explain the return value (e.g., what fields the snapshot contains). It fails to do so, leaving the agent without a clear understanding of what data to expect.

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 description coverage is 100% as the only parameter (group_id) has a description. The tool description does not add any additional semantic information beyond what is already in the input schema, so it meets the baseline expectation.

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 verb 'query' and resource 'course group overview snapshot', indicating a retrieval operation. However, it does not distinguish this tool from sibling tools like query_group_classes or query_group_tasks, which also query group-related information.

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 usage guidelines are provided. The description does not specify when to use this tool over alternatives, nor does it provide any context on prerequisites beyond the parameter hint that group_id comes from query_teacher_groups.

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/Sav1ouR520/xiaoya-teacher-mcp-server'

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