Skip to main content
Glama
Sign In

TutorPing

by ai.tutorping
OverviewDiscussionsAdmin

Search tutors

search_tutors
Read-only

Find independent tutors on TutorPing by subject, student level, and location. Returns tutors with a public page (first name and last initial, subject, level, area, reviews, page link with full details and rates, whether they can be booked directly), how many matching tutors TutorPing has in total with their profiles minus names (request_tutor matches the student with one, optionally a chosen tutorRef), and free TutorPing AI Tutors for the subject (clearly AI, not people; a chat link for help right now). Use for students or parents looking for a tutor (SAT/ACT, math, science, languages, music, and more). If no listed tutor fits, use request_tutor and TutorPing will match one. Always tell the user that an AI tutor is AI.

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": "search_tutors"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNoe.g. "high school", "college"
subjectNoe.g. "SAT", "chemistry", "piano"
locationNoCity or area, e.g. "NYC". Omit for online tutors anywhere.
maxHourlyRateNoUSD per hour

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description usefully adds that results include machine-generated AI tutors that must be disclosed as AI to the user, and that a live chat link is available. That is genuine behavioral guidance not present in the annotations, though it says nothing about result caps, ranking, or rate limits.

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 purpose is front-loaded, but the body is a dense multi-clause paragraph with nested parentheticals that enumerate return fields, making it harder to scan than it needs to be. The material is mostly valuable, yet it would read better as separated sentences covering purpose, returns, and next steps.

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?

With no output schema, the description carries the return contract itself and does so thoroughly: tutor card fields, name-privacy convention, page link with rates, direct-booking flag, total matching counts, and AI tutor links. An agent has everything needed to call it and to interpret the response.

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%, so the schema already documents all four parameters, including the note that location should be omitted for online tutors. The description adds no format or constraint detail for level, subject, or the maxHourlyRate filter, so it sits 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 opening sentence names a specific verb and resource ("Find independent tutors on TutorPing") and scopes it by subject, student level, and location. It also enumerates the fields returned and explicitly distinguishes itself from request_tutor, so an agent can separate it from siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the audience and situation ("Use for students or parents looking for a tutor") and names the concrete alternative with its condition ("If no listed tutor fits, use request_tutor and TutorPing will match one"). The only omission is an explicit when-not-to-use, which is effectively covered by the fallback routing.

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

All TutorPing toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources