Skip to main content
Glama
ilyautov

noname-mcp-ru

by ilyautov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

hh_call_method

Read-only

Execute read-only HeadHunter API operations from the catalog by operation ID, with optional path, query, or body parameters. Returns JSON data without altering anything.

Instructions

Execute one READ endpoint from the catalog by operation_id.

Target API: https://api.hh.ru/openapi/specification/public.

Reads only: nothing here changes data, so it runs without confirmation. To change data use hh_write_method, to delete use hh_delete_method.

Args: operation_id: id from the catalog (see hh_search_methods). path_values: values for {placeholders} in the path. query: query-string parameters. body: JSON request body (a few read endpoints take one). Returns JSON: {"ok": true, "status", "data"} or the error envelope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNo
queryNo
path_valuesNo
operation_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.0
    • removedInput schema / properties / confirm_write
      Removed value: -{
-  "default": false,
-  "title": "Confirm Write",
-  "type": "boolean"
-}
    • removedInput schema / properties / i_understand_this_modifies_data
      Removed value: -{
-  "default": false,
-  "title": "I Understand This Modifies Data",
-  "type": "boolean"
-}
  2. First observedv0.2.0

TDQS

A4.6/5.0
Behavior4/5

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

The description adds useful behavioral context beyond the readOnlyHint annotation, such as 'runs without confirmation' and the return envelope '{"ok": true, "status", "data"} or the error envelope.' This tells the agent the operation is safe and what response shape to expect. There is no contradiction with the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is tightly structured: a one-sentence purpose, a short scope note with explicit alternatives, then a clean bulleted args list. Every sentence earns its place with no filler or repetition.

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?

The description covers the target API URL, read-only scope, execution without confirmation, all argument meanings, and the response/error envelopes. It does not mention authentication specifics or endpoint-specific parameter key constraints, but the sibling tools and output schema fill most gaps. For a generic catalog-driven read executor, this is sufficiently complete.

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 description coverage is 0%, so the description carries full weight for parameter meaning. It explains operation_id as 'id from the catalog (see hh_search_methods)', path_values as 'values for {placeholders} in the path', query as 'query-string parameters', and body as 'JSON request body (a few read endpoints take one).' This is concise and adds real value beyond the unannotated schema.

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: 'Execute one READ endpoint from the catalog by operation_id.' It clearly narrows the scope to read-only operations and distinguishes itself from write/delete siblings by naming them. This goes far beyond the title 'HH read catalog method' and tells an agent exactly what the tool does.

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

Usage Guidelines5/5

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

Explicit usage guidance is provided: 'Reads only: nothing here changes data, so it runs without confirmation. To change data use hh_write_method, to delete use hh_delete_method.' It also tells the agent where to find operation_id by referencing hh_search_methods. This clearly routes the agent to the right tool for the right situation.

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

Deploy Server

Other Tools