Skip to main content
Glama

Look Up Standards by Code

lookup_standards_by_code
Read-onlyIdempotent

Look up Georgia standards by their codes (e.g. ['5.NR.1', '3.T.C.1', 'S8P1', 'SS8H1.a']). Returns the matching standards (each with code, statement, optional notes and path), plus per-code alds (achievement-level descriptions), assessment_coverage (Milestones claim, target, approx_points, qualifier), and assessment_metadata keyed by assessment_id; the server instructions explain how to read points, qualifiers, and levels. A sub-code (e.g. '5.NR.3.3') with no descriptors of its own shows its parent standard's. A current code written another way (lowercase, an MGSE/ELAGSE/CCGPS prefix) is reported in normalized_codes. A retired MGSE math code (K-8 or high school, e.g. 'MGSE5.NF.1', 'MGSE9-12.A.REI.12', 'F.IF.4') is reported in legacy_codes with the current standards the Georgia Department of Education links it to and a status: exact (one standard, same grade), moved (one standard, another grade), or partial (several); every linked standard is in items. Codes that still don't match appear in unknown_codes with likely suggestions.

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": {
      "codes": "<codes>"
    },
    "name": "lookup_standards_by_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo'es' adds Spanish text (Georgia Homeroom's translation; the official standards are English) beside the English fields. Default 'en'.en
codesYesOne or more standard codes, e.g. ['5.NR.1', 'S8P1'].

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / lang
      Added value: +{
      +  "default": "en",
      +  "description": "'es' adds Spanish text (Georgia Homeroom's translation; the official standards are English) beside the English fields. Default 'en'.",
      +  "enum": [
      +    "en",
      +    "es"
      +  ],
      +  "title": "Lang",
      +  "type": "string"
      +}
  2. Changed4 schema fields changed
    • addedInput schema / properties / codes / description
      Added value: +"One or more standard codes, e.g. ['5.NR.1', 'S8P1']."
    • addedInput schema / properties / codes / items / maxLength
      Added value: +40
    • addedInput schema / properties / codes / maxItems
      Added value: +50
    • addedInput schema / properties / codes / minItems
      Added value: +1
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already establish read-only, idempotent, closed-world behavior, but the description adds substantial context beyond them. It discloses normalization behavior, legacy-code resolution with exact/moved/partial statuses, parent fallback for sub-codes without descriptors, and suggestion behavior for unknown codes.

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?

The description is front-loaded with the core purpose and then moves through return fields and special input handling. It is dense and mostly earns its length, though the single long paragraph could be easier to scan if broken into shorter segments.

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?

For a lookup tool with complex code resolution behavior, the definition covers the important edge cases: sub-code fallback, normalized codes, legacy code mapping statuses, and unknown-code suggestions. An output schema exists, so the description need not exhaustively explain return values, and it is complete enough for correct invocation.

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 the schema already documents both parameters, and that sets a baseline of 3. The description nonetheless adds meaningful input semantics by showing accepted code formats and explaining how lowercase, prefixed, retired, or partial codes are handled, though it does not discuss the lang parameter.

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 states a specific verb and resource: look up Georgia standards by their codes. The examples of valid code formats make the retrieval target unambiguous, and exact-code lookup is distinguishable from broader sibling tools like search_standards and browse_standards.

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?

The description clearly implies when to use the tool: when the caller already has standard codes and wants the matching standards and associated assessment data. It also covers unusual inputs such as sub-codes, alternate code formats, retired codes, and unknown codes, but it does not explicitly name alternative tools or state when not to use this one.

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