Skip to main content
Glama

get_country_guide

Assemble a country grading guide: scale table with US 4.0 equivalents, conversion tables, FAQs, common mistakes and confidence/coverage stats.

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

Input Schema

NameRequiredDescriptionDefault
country_codeYesTwo-letter country code (e.g. IN, DE, US)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses what the response contains (tables, FAQs, mistakes, coverage stats), which is genuine behavioral context. However, it says nothing about the cost/latency of assembling a full guide, what happens for unsupported countries, or data freshness — relevant for a composite tool.

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?

One front-loaded sentence with no filler; the enumerated outputs are the most valuable information and come first. The colon-separated list of five items is slightly dense but each item earns its place by previewing the guide's sections.

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 single-parameter tool with no output schema, the enumeration of returned sections effectively stands in for a return description, which is adequate. What is missing is routing guidance against overlapping siblings and any indication of the tool's cost/scope, leaving the agent to guess when a full guide is warranted.

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 coverage is 100% for the single country_code parameter with an example, so the schema does the work. The description mentions 'country' implicitly but adds no format, casing, or unsupported-country guidance beyond the schema, so baseline 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?

States a specific verb ('Assemble') and resource ('country grading guide') and enumerates the components produced: scale table with US 4.0 equivalents, conversion tables, FAQs, common mistakes, confidence/coverage stats. This makes the composite nature clear against siblings like get_grade_mappings or get_us_equivalent, though it never explicitly contrasts itself with them.

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?

There is no when-to-use guidance and no alternatives named, despite heavy overlap with siblings (convert_grade, get_us_equivalent, get_country_grading_systems). The agent must infer that this is the comprehensive option versus the single-purpose ones, which is a real risk given the sibling list.

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.