Skip to main content
Glama
ati-hh-mcp

ati-hh-mcp

by timur-ai

Dict Resume Locales

dict_resume_locales

Retrieves the list of locales supported in hh.ru resumes, so you can validate or select the correct resume language.

Instructions

Get the locales supported in hh.ru resumes.

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": "dict_resume_locales"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the behavioral burden, and "Get" plus the dict_ prefix make clear this is a non-destructive, idempotent read with no side effects. It says nothing about whether the list is static or cached, or what the response items actually contain (codes, names, human-readable labels).

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 no filler. It is appropriately sized for a trivia lookup, though one short clause about the response shape or the dict_locales distinction would cost little and add value.

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 trivial no-param dictionary tool this covers the essentials, but with no output schema the description should say what comes back. The unresolved overlap with the adjacent dict_locales tool is a real completeness gap for an agent choosing between them.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate. Baseline 4 applies for a zero-parameter tool.

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 gives a specific verb and resource ("Get the locales supported in hh.ru resumes"), so an agent knows exactly what it returns. It does not explicitly distinguish itself from the sibling dict_locales, which presumably returns the broader locale list, leaving a mild ambiguity.

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

Usage Guidelines3/5

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

No when-to-use or when-not-to-use guidance is given, and no alternative is named. For a zero-parameter dictionary lookup the implied usage is fairly obvious, but the agent must infer the distinction from dict_locales and dict_languages on its own.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.