Skip to main content
Glama
Sign In
TIA Portal MCP Server

TIA Portal MCP Server

by BJM1122
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List TIA Export Indexes

tia_list_export_indexes
Read-onlyIdempotent

Lists compact export snapshot summaries under bounded project roots, returning the current or latest indexed snapshot with failure details and optional history while skipping test directories.

Instructions

List compact export summaries under bounded roots. By default each project scope returns its valid current snapshot, or its latest indexed snapshot with the current-pointer failure reason; historyCount counts all snapshot directories. includeHistory shows all snapshots. Child directories starting with '_' are tool test directories: skipped by default and always excluded from automatic matching; the search root itself is exempt. _codex_index is always skipped. omitted counts collapsed history snapshots, skipped test directories, project-filtered entries, and matching entries beyond maxResults; project filters run before maxResults. Explicit listing never makes an invalid or historical snapshot eligible for automatic matching.

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

Input Schema

NameRequiredDescriptionDefault
rootsNo
maxResultsNo
projectNameNoCase-insensitive substring of summary.projectName.
projectPathNoExact summary.projectPath after path normalization (case-insensitive on this Windows server).
includeHistoryNo
includeTestSnapshotsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.29.1

TDQS

A4/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, it discloses several behaviors an agent could not infer: '_'-prefixed test directories are skipped by default and always excluded from automatic matching with the search root exempt, _codex_index is always skipped, and omitted counts collapsed history, skipped test dirs, project-filtered entries, and over-limit matches. It also clarifies that explicit listing never makes an invalid or historical snapshot eligible for automatic matching, which prevents a real misuse.

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?

Front-loaded with the core behavior, then details in rough order of importance, and each sentence carries non-redundant information. The prose is dense and semicolon-heavy, which slightly hurts readability but not enough to waste space.

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?

With no output schema, the description does well to name the fields an agent will see (valid current snapshot, latest indexed snapshot with failure reason, historyCount, omitted). Only the shape of roots results and default root behavior remain unstated, a minor gap for a six-parameter listing tool.

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 coverage is only 33%, but the description compensates by explaining includeHistory, includeTestSnapshots (via the '_' directory rule), maxResults truncation, and the ordering of project filters. roots and the exact filter semantics for projectName/projectPath are left to the schema, so it is strong but not fully compensating.

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 opening sentence gives a specific verb and resource ("List compact export summaries under bounded roots") and states the default snapshot semantics. It does not explicitly differentiate itself from siblings like tia_read_export_index, but the listing-versus-reading distinction is implied clearly enough.

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 description reliably explains the default mode and the effect of includeHistory, plus the ordering of project filters relative to maxResults. It never states when an agent should prefer another tool or when this listing is inappropriate, so guidance remains implied rather than explicit.

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