Skip to main content
Glama

How to cite and reuse the word lists

get_citation
Read-only

Returns how to cite and reuse the dataset: license (name, URL, note; CC BY 4.0 for the compilation, the Dolch words are public domain), citeAs text, the source page, the data's updated date and the fixed CSV and JSON download URLs on dyslexiasteps.com that hold every list. Use this when someone reuses, prints or redistributes the lists; use get_placement_basis instead to explain how grades were assigned.

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_citation"
  }
}

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 readOnly and closed-world, so the safety profile is covered; the description adds real context by naming the license terms (CC BY 4.0 for the compilation, public domain for Dolch words) and the fixed external URLs. It does not mention caching or freshness beyond the 'updated date' field, which is a minor gap.

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-loaded with the main purpose, then the returned fields, then the usage routing. It is dense but every clause carries information; the parenthetical license note is slightly verbose but relevant.

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 compensates by itemizing the returned fields, which is exactly what an agent needs to know before calling. Usage routing and license specifics round it out fully.

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?

The tool takes zero parameters, so the baseline is 4; there is no parameter meaning for the description to add or omit.

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 how to cite and reuse the dataset') and then enumerates the exact payload: license name/URL/note, citeAs text, source page, updated date, and download URLs. This is clearly distinct from the sibling tools that deal with word lists and placements.

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?

Gives an explicit trigger ('when someone reuses, prints or redistributes the lists') and names the alternative for a different need ('use get_placement_basis instead to explain how grades were assigned'). Both when-to-use and when-not-to-use are covered.

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.