Skip to main content
Glama

get_country_grading_systems

Get the grading systems for a country, with their grade mappings.

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": {
      "country_code": "<country_code>"
    },
    "name": "get_country_grading_systems"
  }
}

Input Schema

NameRequiredDescriptionDefault
country_codeYesTwo-letter country code (e.g. IN, DE, US)
include_mappingsNoInclude grade mappings for each system (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the entire burden of behavioral disclosure. "Get" implies a read, and "with their grade mappings" hints the payload is nested, but there is no statement about permissions, whether the call is scoped to a single country, or what happens for an unknown or unmapped country code.

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?

A single front-loaded sentence with zero filler, and the resource and payload are both stated up front. Brevity here is efficient rather than under-specified for such a simple read.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with full schema coverage and no output schema, the description is adequate but thin. It omits edge-case behavior (unknown country, empty result) and the shape of the returned systems that an agent would need to chain further calls.

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?

Schema description coverage is 100%, so country_code's format (two-letter, with examples) and include_mappings' default are already documented in the schema. The phrase "with their grade mappings" loosely corresponds to include_mappings but adds no syntax or behavior beyond what the schema states.

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?

"Get the grading systems for a country" states a specific verb and resource, plus the returned payload includes grade mappings. It is clear on its own, but it does not distinguish itself from nearby siblings such as get_grade_mappings or resolve_grading_scale, which an agent could plausibly confuse with this tool.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance, no exclusions, and no mention of the sibling tools that compete for the same intent. The agent must infer the boundary from the tool name alone.

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.