Skip to main content
Glama

nittim

by com.nittim
OverviewDiscussionsAdmin

Preview an Upload Before Any Source Leaves the Machine

preview_upload

NEEDS A KEY: mint one at https://nittim.com/keys. Send the paths and sizes of the files you would post — no content leaves your machine to ask this — and get back the list, the byte count, and a link for the account owner to approve it. Free. The approval covers that file list and no other, and a paid audit's own confirmation already covers the file list beside the price, so approving ahead of time is optional.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesA display label for this project, e.g. 'my-abacus-app'. Sanitized before use.
filesYesPaths and sizes only — the same set you would post. Never file content.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"A display label for this project, e.g. 'my-abacus-app'. Sanitized before use — no path/URL characters needed."New value: +"A display label for this project, e.g. 'my-abacus-app'. Sanitized before use."
  2. Added

TDQS

B3.2/5.0
Behavior3/5

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

The description discloses that only paths and sizes are sent, that no content leaves the machine, and that a link is returned for owner approval. However, it does not clarify whether this creates server-side state despite readOnlyHint=false, and the repeated approval/audit wording is confusing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is verbose and repetitive, especially the trailing sentences about approval coverage and paid audits. Key information is buried in promotional phrasing, making it harder to parse quickly.

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?

There is no output schema and the description only vaguely lists 'the list, byte count, and link.' It also omits how the required key is transmitted, which is essential for actually invoking the tool.

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?

Both parameters are described with meaningful constraints: name is a sanitized display label and files is explicitly limited to paths and byte counts, never content. This goes beyond the bare schema and clarifies the no-content promise.

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?

Clearly names the operation as previewing an upload before source/content leaves the machine and specifies the resource (the file set). It is distinguishable from sibling audit/scan tools by focusing on upload preview and approval.

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 description explains that it requires a key and should be used before posting files, but it does not explicitly contrast it with alternatives or explain when not to use it. It also fails to say how the key is supplied.

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

All nittim toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources