Skip to main content
Glama
kompas-mcp

kompas-mcp

by biryak

List open documents

doc_list
Read-onlyIdempotent

Lists open KOMPAS documents with fresh handles, type, path, and active/changed/read-only flags; refresh handles here after reconnects.

Instructions

Documents open in KOMPAS with their handles, type, path, active/changed/read-only flags. Handles change when the server reconnects; always take fresh ones from here.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add non-obvious context — and it does, disclosing that handles are invalidated on server reconnect and must be re-acquired. It does not mention ordering, count limits, or handling of zero open documents, which keeps it from a 5.

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 sentences, zero filler. The return contents come first and the handle-lifecycle warning second, which matches the order an agent needs them.

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 correctly takes on the burden of enumerating return fields and the handle-invalidation caveat, which is the critical gotcha for this tool. Minor omissions (ordering, whether all document types are included) are not enough to make calling it ambiguous.

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 there is no argument semantics to explain; the baseline for a parameterless tool applies. The description instead spends its words on the shape of the result, which is the more useful information here.

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 the specific resource (documents open in KOMPAS) and enumerates exactly what comes back: handles, type, path, and active/changed/read-only flags. The verb is implied by the tool name rather than stated, and siblings like doc_open/doc_close are not referenced, so it stops just short of a 5.

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 sentence 'always take fresh ones from here' prescribes a workflow: fetch handles before operating on a document. That is useful implied guidance, but there is no explicit when-to-use/when-not-to-use framing or comparison to alternatives such as selection_get for identifying objects.

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