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

live-mcp-for-1c

by vlikhobabin

get_service_info

Retrieve AIDataRead service version, endpoints, authentication requirements, limits, and capabilities to verify configuration and plan read-only 1C queries.

Instructions

Read AIDataRead version, endpoints, auth, limits, and capabilities.

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

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?

No annotations exist, so the description carries the full burden. It does signal a read-only, side-effect-free operation ("Read") and discloses the categories of information returned, but it says nothing about whether calling it itself requires credentials, whether results are cached, or any rate/latency characteristics — notable gaps for a tool whose whole subject is auth and limits.

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, which is appropriately sized for a zero-parameter introspection tool. The terseness borders on cryptic, though — terms like "capabilities" and "limits" are listed without any indication of what they concretely mean.

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?

With no output schema and no annotations, the description is the only source of information about the response, and it names the content categories but not their shape or format (e.g., is 'endpoints' a list of URLs, a map of region to URL?). For a simple zero-param tool this is adequate but leaves an agent guessing at the return structure.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. The schema (additionalProperties: false) already makes the no-argument contract unambiguous.

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 uses a specific verb ("Read") plus an enumerated resource list (version, endpoints, auth, limits, capabilities) of the AIDataRead service, so an agent knows exactly what comes back. It does not distinguish itself from the sibling ping_service, which likely overlaps as a connectivity/metadata check, leaving the choice between the two to inference.

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?

Usage is only implied: the enumeration of returned facts (endpoints, auth, limits) lets an agent infer 'call this when I need connection details,' but there is no explicit when-to-use statement, no prerequisites, and no exclusion relative to ping_service or the query-execution siblings.

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