Skip to main content
Glama
Sign In
./skimread

./skimread

by avikchakraborty060-create
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list

Retrieve recent skimread runs with IDs, commands, exit codes, and sizes, optionally limited, to review prior command outputs.

Instructions

List recent runs stored by skimread (id, command, exit code, size).

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses the shape of returned records (id, command, exit code, size), which is useful, but says nothing about ordering guarantees, what 'recent' means, default limits, or pagination behavior.

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?

One tight, front-loaded sentence with no wasted words. It is efficient, though arguably terse enough to omit needed detail.

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

Completeness3/5

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

For a simple one-parameter list tool with no output schema or annotations, naming the returned fields covers a lot of ground, but the unexplained 'limit' parameter and undefined 'recent' semantics leave real gaps.

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?

The single 'limit' parameter has 0% schema description coverage and is never mentioned in the description. 'Recent' hints at a cap but gives no meaning, default, or range, so the description does not compensate for the schema gap.

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+resource ('List recent runs stored by skimread') and even enumerates the returned fields, so the agent knows exactly what it gets. It does not explicitly differentiate itself from siblings like show or run, but the resource is clear enough to distinguish a listing operation.

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 when-to-use guidance, no mention of alternatives such as show or run, and no prerequisites or exclusions. The agent must infer that this is the enumeration counterpart to the other tools.

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