Skip to main content
Glama
tydude001

proofcut

by tydude001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

pack_show

Read-onlyIdempotent

Inspect a pack's declared contents from its file, a project's applied snapshot, or compare both to find differences.

Instructions

What a pack declares — from its file, a project's snapshot, or both.

pack_path alone reads and resolves the file fresh, needing no project (card_templates's own shape). path alone reports what a project actually has applied, from its stored snapshot — never the file again. Both together compares "what the file says now" against "what the project is still running."

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoA project directory, or nothing. Omitting it means *no project* here — never the bound one — so `pack_path` alone reads the file fresh; given, it reports what that project has applied.
variantNoReport one variant rather than all of them.
pack_pathNoRead and resolve this pack file fresh, needing no project. With `path` as well, it compares what the file says now against what the project is still running.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv0.25.0
    • removedInput schema / properties / pack_path / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / pack_path / description
      Added value: +"Read and resolve this pack file fresh, needing no project. With `path` as well, it compares what the file says now against what the project is still running."
    • removedInput schema / properties / pack_path / title
      Removed value: -"Pack Path"
    • addedInput schema / properties / pack_path / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / properties / path / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / path / description
      Added value: +"A project directory, or nothing. Omitting it means *no project* here — never the bound one — so `pack_path` alone reads the file fresh; given, it reports what that project has applied."
    • removedInput schema / properties / path / title
      Removed value: -"Path"
    • addedInput schema / properties / path / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / properties / variant / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / variant / description
      Added value: +"Report one variant rather than all of them."
    • removedInput schema / properties / variant / title
      Removed value: -"Variant"
    • addedInput schema / properties / variant / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / title
      Removed value: -"pack_showArguments"
  2. First observedv0.24.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds behavioral context beyond annotations: it explains that path alone reads from the stored snapshot and never the file again, and that pack_path alone reads and resolves the file fresh. This clarifies the data source behavior, which is valuable. It doesn't describe output format, but an output schema exists, so that's not required.

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?

The description is compact and front-loaded: the first sentence states the core purpose, and the following sentences explain the three modes without redundancy. Every sentence earns its place, and the structure makes the mode distinction immediately clear.

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

Completeness5/5

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

For a read-only inspection tool with three optional parameters, an output schema, and full schema description coverage, the description is complete. It explains all three usage modes, the data sources involved, and the comparison semantics. Nothing an agent needs to select and invoke the tool correctly is missing.

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 description coverage is 100%, so the schema already documents all three parameters. The description adds meaning by explaining the interaction between path and pack_path: how they combine to compare file state vs. project state, and that omitting path means no project. This goes beyond the individual parameter descriptions and clarifies the semantic relationship between parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: reporting what a pack declares from its file, a project's snapshot, or both. It distinguishes three modes (pack_path alone, path alone, both together) with specific verbs and resources. This differentiates it from siblings like pack_apply, pack_activate, and pack_status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly explains when to use each mode: pack_path alone for reading a file fresh without a project, path alone for reporting what a project has applied, and both together for comparing file state vs. project state. It also clarifies that omitting path means no project, never the bound one, which prevents a common misuse.

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