Skip to main content
Glama

US schools in a city from GreatSchools: name, GreatSchools

education_greatschools
Read-only

US schools in a city from GreatSchools: name, GreatSchools rating (1-10) and label, sub-ratings (test scores, student progress, equity...), school type (public, charter, private), grade levels, district, address, enrollment, students per teacher, % low-income, parent rating and review count, coordinates and profile URL, plus the total number of schools. Filter by level (preschool, elementary, middle, high) and type; 25 per page, best rated first. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "state": "<state>",
      "city": "<city>"
    },
    "name": "education_greatschools"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity name, e.g. San Francisco, Austin (required)
pageNoResults page from 1 (default 1)
typeNoOptional: public, charter or private
levelNoOptional: preschool, elementary, middle or high
stateYesUS state code, e.g. CA, TX, NY (required)

Output Schema

NameRequiredDescriptionDefault
cityNo
pageNo
typeNo
countNo
levelNo
stateNo
totalNo
sourceNo
schoolsNo
checkedAtNo
totalPagesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint, the description discloses the cost model ($0.002 per successful call), the payment rail (x402, USDC on Base/Solana), that failed calls are not charged, and the page size and sort order. That is genuinely useful operational context; it falls short of 5 only because it doesn't cover rate limits or behavior when a city returns nothing.

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?

Purpose and pricing are front-loaded, which is good, but the middle of the description is a long comma-run enumeration of return fields that duplicates the output schema, and the cost sentence is dense enough to obscure the paging rule buried beside it.

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?

With a full output schema, complete input schema coverage, and annotations, the description only needs to add cost, filtering, and ordering semantics — which it does. The omission of paging-termination or empty-result behavior keeps it just shy of complete for a paid, paginated tool.

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%, so the schema already documents all five parameters. The description restates the same level and type values rather than adding new syntax or constraints, so it neither compensates for nor exceeds the schema — baseline 3 applies.

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 opens with a specific verb+resource+scope: US schools in a city from GreatSchools, with named data fields rendered. An agent can tell instantly this is a location-scoped school directory lookup, not a generic search or business-directory tool like the b2b/health siblings.

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?

It states the required state/city and the available filters (level, type) and that results are paged 25 at a time, best rated first, which implies the usage context. But there is no explicit when-to-use/when-not guidance, no note on what to do for a zero-result city, and no mention of paging until exhaustion.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources