Skip to main content
Glama

tutoring

by io.github.LouisVanh

Search tutors

search_tutors
Read-only

Search iTutorOnline's verified tutor directory. Filter by subject/keyword, country, spoken language, max hourly price (EUR), and minimum rating. Returns ranked tutor cards with rates, ratings, and profile links.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many tutors to return (1-25, default 8).
countryNoFilter by tutor country, e.g. "Germany", "Netherlands", "Belgium".
subjectNoSubject or keyword, e.g. "Mathematics", "IELTS", "Python". Synonyms and NL/FR/DE translations are matched. See list_subjects.
languageNoFilter by a language the tutor speaks, e.g. "English", "Dutch", "French".
minRatingNoOnly tutors with an average review score at or above this (0-5).
maxPriceEurosNoOnly tutors at or below this hourly rate in euros.

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already indicate read-only, open-world, non-destructive. Description adds 'verified directory' and 'ranked results' but little extra on pagination or costs.

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?

Three efficient sentences: action, filters, output. No wasted words.

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?

Covers purpose, filters, and return type. Could mention sorting order, but adequate for a search tool without output schema.

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 covers 100% of parameters with descriptions. Tool description repeats filter types without adding new information about parameter behavior.

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?

Clearly states the tool searches a tutor directory with specific filters and returns ranked results. Distinct from siblings like get_tutor (single tutor) or list_subjects.

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?

Implies use for finding tutors but lacks explicit when-not-to-use or comparison with siblings. Mentions list_subjects for subject choices but no further guidance.

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

All tutoring toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool addresses a distinct task: info, search, profile detail, reviews, subjects, self-serve booking prep, and human-assisted requests. Even the two booking-related tools are clearly separated by their descriptions and outcomes.

Naming Consistency5/5

All tools follow a consistent lowercase snake_case verb_noun pattern such as get_tutor, list_subjects, search_tutors, prepare_booking, and request_human_tutor. The naming makes the function of each tool predictable.

Tool Count5/5

Seven tools is a well-scoped set for a tutoring platform integration. Each tool addresses a meaningful part of the user journey without redundancy or bloat.

Completeness4/5

The surface covers platform info, discovery, evaluation, subject lookup, and both self-serve and human-assisted booking paths. A minor gap is the absence of direct booking management or tutor availability checks, but these are not required for the primary workflow.

Resources