Skip to main content
Glama
SP6 MCP

SP6 MCP

by HANJUSON

sp6_file_inspect

Read-onlyIdempotent

Inspect .ksp6/.fmlt keyboard backup files to hash, inventory, and list objects with paging and ID filters, so you can examine file contents before editing or validating data.

Instructions

Hash, inventory and a paged object list of a .ksp6/.fmlt file.

path is relative to the work root or absolute. Empty records in a file do NOT prove the keyboard slot is empty.

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": {
      "path": "<path>"
    },
    "name": "sp6_file_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoall
pageNo
pathYes
id_maxNo
id_minNo
page_sizeNo
include_emptyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

C2.9/5.0
Behavior3/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 bar is lower. The description adds real value by disclosing the three result components, that listing is paged, and a non-obvious interpretation trap about empty records, but it says nothing about pagination termination, whether pages cover the whole file, or how id ranges interact with the list.

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?

Two tight sentences, front-loaded with the core capability, with the caveat separated into its own paragraph. Nothing is redundant, though the first sentence packs three distinct outputs into one clause without ordering them.

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?

A 7-parameter tool with no output schema and zero schema descriptions needs the description to explain filtering and paging semantics, and it does not. An agent can call it with just a path, but cannot confidently use kind, id_min/id_max, or include_empty without guessing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and largely fails it: kind, page, page_size, id_min, id_max, and include_empty are all undocumented in both places. Only path gets meaning ('relative to the work root or absolute'), and 'paged' hints at page/page_size without explaining defaults or ordering.

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 names the concrete outputs (hash, inventory, paged object list) and the exact file types (.ksp6/.fmlt), so an agent knows what it gets back. It stops short of differentiating itself from siblings like sp6_multi_read or sp6_object_find, and 'inventory' remains an undefined term.

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?

There is no guidance on when to choose this over sp6_multi_read, sp6_object_find, or sp6_multi_validate. The only directional statement is an interpretive caveat ('Empty records ... do NOT prove the keyboard slot is empty'), which is useful but is about reading results, not about tool selection.

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