Skip to main content
Glama

Trace a Strand Across Grades

get_vertical_progression
Read-onlyIdempotent

Compare one strand year over year, for pacing, remediation, and differentiation. Pass a code (e.g. '5.NR.1') to line that standard up against the same code at every grade ('3.NR.1', '4.NR.1', ...), or pass subject + strand_code (name or code) for the whole strand. Returns grades, each with grade, grade_label, and standards (code, statement, and gmas/ald flags). The trace matches codes by shape; state_links lists the steps (from, to) that Georgia's own data also links grade to grade (ELA only). If the strand can't be identified, the result is an error.

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

Input Schema

NameRequiredDescriptionDefault
codeNoA standard code to trace, e.g. '5.NR.1'.
subjectNoSubject: 'ela', 'math', 'science', or 'social_studies'. Use with strand_code.
strand_codeNoStrand code ('NR') or name ('Numerical Reasoning'). Use with subject.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / code / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maxLength": 40,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / code / description
      Added value: +"A standard code to trace, e.g. '5.NR.1'."
    • changedInput schema / properties / strand_code / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maxLength": 100,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / strand_code / description
      Added value: +"Strand code ('NR') or name ('Numerical Reasoning'). Use with subject."
    • changedInput schema / properties / subject / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "ela",
      +      "math",
      +      "science",
      +      "social_studies"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / subject / description
      Added value: +"Subject: 'ela', 'math', 'science', or 'social_studies'. Use with strand_code."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the bar is low — yet the description adds matching semantics ('matches codes by shape'), a caveat that `state_links` reflects Georgia's own grade-to-grade links for ELA only, and an explicit failure mode when the strand can't be identified. These are exactly the non-obvious traits an agent could not infer from structured fields.

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?

Four sentences, front-loaded with purpose and calling modes, with no filler. The return-shape sentence (`grades`, `grade`, `grade_label`, `standards`) partially restates what the output schema already declares, which is the only thing keeping it from a 5.

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?

For a read-only, output-schema-backed trace tool this covers modes, matching logic, a data-coverage caveat, and the error path — everything needed to call it correctly. Minor over-explanation of return fields is the only redundancy; no permissions or pagination concerns apply.

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?

Schema coverage is 100%, so baseline is 3; the description earns more by clarifying the either/or contract between `code` and `subject`+`strand_code` and by noting strand_code accepts a name ('Numerical Reasoning') or a short code ('NR'). The code example ('5.NR.1') reinforces the expected code shape beyond the schema's bare maxLength.

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 and resource: 'Compare one strand year over year', and the code-vs-strand duality makes the scope unambiguous. No sibling tool (get_standard_details, lookup_standards_by_code, search_standards) performs a cross-grade trace, so an agent can route here without opening any schema.

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 concrete use cases (pacing, remediation, differentiation) and explicitly routes between two calling modes: pass `code` for a single standard's vertical lineup, or `subject` + `strand_code` for the whole strand, each with a worked example. It stops short of naming when to prefer a sibling tool such as lookup_standards_by_code for a single-grade lookup.

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