Skip to main content
Glama

Katip klasörümü aç

open_folder
Idempotent

Opens Katip's default folder in Finder or Explorer and creates it if missing, so legal documents can be located or moved without extra steps. Documents stay searchable in the case folder and Downloads.

Instructions

Katip'in varsayılan klasörünü Finder'da ya da Gezgin'de açar, yoksa oluşturur. Belgeleri buraya taşımak gerekmez: Katip dava klasöründe ve İndirilenler'de de arar.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing the concrete side effect: a folder may be created if missing, which explains the non-readOnly profile while the idempotent behavior is explicitly named. It also clarifies the local scope (Finder/Explorer), consistent with openWorldHint=false. It does not say what is returned or how failure is reported.

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 short sentences, with the primary action and the create-if-missing caveat front-loaded, followed by the one caveat an agent would otherwise get wrong. No redundant or filler wording.

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?

For a zero-parameter tool with no output schema, the description covers what happens and why it matters, which is most of what an agent needs. The remaining gap is the return value or confirmation signal the caller receives after the folder is opened.

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?

The tool takes zero parameters, so per the baseline this dimension is a 4; however there is nothing parameter-related for the description to add. Scored conservatively because the description offers no argument semantics beyond scope hints.

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?

States a specific verb and resource ("opens Katip's default folder") plus platform targets (Finder/Explorer) and a side effect (creates it when absent). It implicitly separates itself from file-listing or search siblings by telling the agent not to relocate documents, though it never names an alternative tool.

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 second sentence gives contextual guidance (no need to move documents here, since Katip searches the case folder and Downloads), which implies when this tool is and isn't necessary. However, there is no explicit statement of when to call it versus a sibling such as list_files, so usage is inferred rather than directed.

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