Skip to main content
Glama

How grades were assigned

get_placement_basis
Read-only

Returns the full table of grade-placement sources, document-level and not per word: bases (each with kind, code, summary and source URL), the grade ids with labels and typical ages, the limits note and the methodology page. Sources are Dolch's own grade levels (1936, public domain), the Common Core Foundational Skills item that names the skill, or a typical sequence when no standard names it. Placement is per list: match a list's placementBasis code (from list_word_lists or get_word_list) to a code here. Use this to explain why a list sits at a grade; use get_citation instead for license and reuse.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with a static, closed reference lookup. It adds value beyond annotations by disclosing the granularity ('document-level and not per word') and the provenance of the sources (Dolch 1936 public domain, Common Core item, typical sequence). It stops short of noting stability or that the table is a fixed dataset, so not a 5.

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

Conciseness4/5

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

Front-loads the return contents, then the code-joining rule, then the when-to-use and the alternative — a logical order. The middle sentence enumerating bases and grade fields is dense but earns its place given there is no output schema; slightly long overall.

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-shape burden and does so: it lists each section of the response and explains how to join the returned codes to list data. For a zero-parameter, read-only reference tool, nothing an agent needs in order to call and interpret it is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero input parameters, and the description correctly implies a parameterless call while explaining how the caller connects conceptually — via a placementBasis code obtained from list_word_lists or get_word_list. That code-linking is genuinely useful semantics even though nothing is passed in.

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?

States a specific verb and resource ('Returns the full table of grade-placement sources') and immediately scopes it ('document-level and not per word'). It also enumerates the payload sections (bases, grade ids, limits note, methodology page), so an agent knows exactly what it is getting, distinct from get_word_list or get_citation.

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?

Explicit routing: 'Placement is per list: match a list's placementBasis code (from list_word_lists or get_word_list) to a code here.' It says when to use it ('to explain why a list sits at a grade') and names the alternative for a different need ('use get_citation instead for license and reuse'), covering both use and exclusion.

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.