Skip to main content
Glama

Get a school's instructions

get_school_instructions
Read-onlyIdempotent

The school's skill file (its rules, prompts and flow, read this first) and its live schema (fields, enums, item types, checklist). Fetch once per session per school.

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": {
      "school": "<school>"
    },
    "name": "get_school_instructions"
  }
}

Input Schema

NameRequiredDescriptionDefault
schoolYesThe school's slug from list_schools, e.g. "vvs"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds value beyond them by disclosing caching semantics ('once per session per school') and by characterizing the payload as both static rules and a 'live' schema, which tells the agent the data may change between sessions.

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?

Two dense sentences with no filler; the primary payload is front-loaded and the caching constraint closes it out. The nested parentheticals make it slightly harder to parse than a flat statement, but nothing is wasted.

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 no output schema, the description carries the burden of explaining the return value and does so well, enumerating both the rules/prompts and the field/enum/checklist metadata. It omits what happens with an invalid slug or a school lacking instructions, a minor gap for a simple one-parameter read.

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?

There is a single parameter with 100% schema description coverage, including the slug pattern and the pointer to list_schools. The description adds no meaning beyond the schema for this parameter, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the concrete resources fetched: a skill file (rules, prompts, flow) plus a live schema (fields, enums, item types, checklist). That is far more specific than the title alone and distinguishes it from siblings like get_status or list_schools, though the returning verb ('fetch') appears only implicitly in the last sentence.

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

Usage Guidelines4/5

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

It gives explicit operational guidance: 'read this first' establishes priority, and 'Fetch once per session per school' prevents redundant calls. It does not name an alternative tool or exclusion, but the when-and-how-often guidance is concrete.

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.