Skip to main content
Glama
Sign In
INFATON MCP35

INFATON MCP35

Official
by infaton
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

generate_report

Generate tabular reports from arbitrary queries. Provide a query and optional title to receive structured data.

Instructions

Сформировать простой отчёт по произвольному запросу. Возвращает табличные данные.

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": {
      "query": "<query>"
    },
    "name": "generate_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesТекст запроса для отчёта
titleNoЗаголовок отчёта (необязательно)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so description must convey behavioral traits. It only states it returns tabular data, but does not disclose whether it is read-only, what permissions are needed, or any side effects. The term 'report' implies a potentially complex operation, but no details are given.

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?

Two concise sentences with no wasted words. The key information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, the description should provide more context about the report structure, query language, and limitations. It is vague for a tool with potential complexity, especially compared to more specific siblings.

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?

Input schema covers both parameters with descriptions. Description adds minimal extra value by noting 'arbitrary query', but does not provide formatting examples or constraints beyond the schema.

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?

Description clearly states it generates a simple report from an arbitrary query and returns tabular data. It distinguishes itself from siblings like get_balance or get_list by being a generic report generator, though it doesn't explicitly name alternatives.

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?

No guidance on when to use this tool versus other data retrieval tools like execute_query or get_list. Does not mention prerequisites, when not to use, or context for the report.

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