Skip to main content
Glama
EquateItAu

ClassQuill MCP server

by EquateItAu

list_tutor_tiers

Read-onlyIdempotent

Retrieve tutor tiers from ClassQuill's tutoring-business data. Use pagination to browse through available tiers and their details.

Instructions

List Tutor Tiers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoRecords per page (default 20, max 100)
offsetNoPagination offset

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
metaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. However, the description adds zero behavioral context beyond the annotations — no mention of pagination behavior, data scope, or any operational traits.

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

Conciseness2/5

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

The description is only four words and adds no informational value beyond the tool name. It is under-specified rather than genuinely concise — it could have been omitted entirely with no loss of clarity.

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?

While the output schema and parameter schema exist, the description leaves the concept of 'tutor tiers' undefined and provides no guidance on when the result set is needed. For a list tool the definition is minimal but still missing the core meaning of the resource.

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%; both limit and offset are documented with meaning. The description itself provides no additional parameter context, but the high schema coverage justifies the baseline score of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List Tutor Tiers' is a tautology — it restates the tool name and title verbatim without adding any detail about what a tutor tier is or how this listing differs from sibling list tools. It names a verb and resource but provides no differentiating 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?

There is no guidance about when to use this tool versus alternatives such as list_tutors or list_students. The description gives no context, preconditions, or exclusions, leaving the agent to infer usage entirely from the tool name.

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