Skip to main content
Glama
live-mcp-for-1c

live-mcp-for-1c

by vlikhobabin

ping_service

Verifies AIDataRead service availability via GET /ping/ to confirm the endpoint is reachable before running read-only 1C queries.

Instructions

Check AIDataRead service availability through GET /ping/.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 full disclosure burden. It does reveal the HTTP verb GET, which implies a safe read-only call with no side effects, but it says nothing about authentication requirements, rate limits, timeouts, or what a successful vs failed response looks like.

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?

A single short sentence with the purpose front-loaded and zero filler. Nothing could be removed without losing meaning.

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 parameterless health check this is close to sufficient, but with no output schema the description should indicate what a ping returns (status payload, success indicator) so an agent knows how to interpret the result.

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 zero parameters, so the baseline is 4; there is no argument semantics for the description to clarify and it correctly makes no claims about inputs.

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?

Names a specific verb ("Check") and resource ("AIDataRead service availability") plus the underlying endpoint GET /ping/, so an agent can tell this is a health probe rather than a data query. It is distinguishable from siblings like get_service_info by being an availability check, though the boundary with that sibling is not spelled out.

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?

The phrasing implies the use case — verifying the service is reachable before issuing real queries — but there is no explicit when-to-use/when-not statement and no pointer to alternatives such as get_service_info. Adequate implied guidance only.

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