Skip to main content
Glama

nittim

by com.nittim
OverviewDiscussionsAdmin

Audit Posted Source (no GitHub repo required)

audit_source

Paid nittim AI audit of source files you post, for a project with no GitHub remote. Send SOURCE files, not build output — no node_modules or dist. On nittim's own key this answers with the audit's id; the report lands Usually within 15 minutes*. * Most reports land within 15 minutes. Worst case, 24 hours. On your own key (BYOK Pro) the report comes back in this call instead. Costs 5.14 credits (a paid+subscribed org's included allowance, an unspent Audit, then prepaid credits), always saved as a PRIVATE report. fullScan: true buys the wider Full Audit tier. NEEDS A KEY: mint one at https://nittim.com/keys. COSTS MONEY in three calls: the first quotes a price and charges nothing; a second with confirmedCost set to that exact price returns a one-time link for the ACCOUNT OWNER to confirm — their yes, not the assistant's; a plain third call with the same arguments runs once at that price. A moved price is re-quoted, never charged.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesA display label for this project, e.g. 'my-abacus-app'. Sanitized before use.
filesYesSource files as { path, content }[] — not build output. At most 1000; over the internal per-audit cap, the highest-priority ones win.
fullScanNoTrue buys the wider Full Audit tier over the files you post, priced by pass count.
uploadGrantNoOptional: the id of an upload approval the account owner already confirmed. A large post without one is answered with a confirmation covering the files and the price.
authorizationNoHUMAN CONFIRMATION. The `authorization` id from the confirm-link answer, once the account owner has pressed Confirm. Single-use, short TTL.
confirmedCostNoCOST CONFIRMATION. Omit on the first call; then send back the exact quoted `cost`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • changedInput schema / properties / authorization / description
      Previous value: -"HUMAN CONFIRMATION. Omit until the account owner has pressed Confirm on the link a paid tool answered with; then set to that answer's `authorization` id (single-use, short TTL). Protocol: server instructions."New value: +"HUMAN CONFIRMATION. The `authorization` id from the confirm-link answer, once the account owner has pressed Confirm. Single-use, short TTL."
    • changedInput schema / properties / confirmedCost / description
      Previous value: -"COST CONFIRMATION. Omit on the first call (it only quotes); then set to the exact `cost` object quoted. A moved price is re-quoted, never charged. Protocol: server instructions."New value: +"COST CONFIRMATION. Omit on the first call; then send back the exact quoted `cost`."
    • changedInput schema / properties / confirmedCost / properties / centicredits / description
      Previous value: -"Copy the `centicredits` integer from the cost this tool quoted you, if it has one. Omit it if the quote did not carry one."New value: +"The `centicredits` integer from the quoted cost, if it carried one."
    • changedInput schema / properties / confirmedCost / properties / credits / description
      Previous value: -"Copy the `credits` number from the cost this tool quoted you."New value: +"The `credits` number from the quoted cost."
    • changedInput schema / properties / confirmedCost / properties / kind / description
      Previous value: -"Copy the `kind` from the cost this tool quoted you, e.g. 'credits'."New value: +"The `kind` from the quoted cost, e.g. 'credits'."
    • changedInput schema / properties / files / description
      Previous value: -"The source files to audit, as { path, content }[]. Send SOURCE files, not build output (no node_modules, no dist/build, no binaries) — pre-filter before posting. At most 1000 files; the highest-priority ones (manifests, lockfiles, CI config, .env-shaped files, server-execution routes) win if you're over the internal per-audit cap."New value: +"Source files as { path, content }[] — not build output. At most 1000; over the internal per-audit cap, the highest-priority ones win."
    • changedInput schema / properties / files / items / properties / content / description
      Previous value: -"The file's full text content."New value: +"The file's full text."
    • changedInput schema / properties / fullScan / description
      Previous value: -"True buys the wider Full Audit tier instead of the default Audit, over the files you post: every eligible file, priced by pass count."New value: +"True buys the wider Full Audit tier over the files you post, priced by pass count."
    • 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."
    • changedInput schema / properties / uploadGrant / description
      Previous value: -"The id of an upload approval the account owner has already confirmed. Optional: a post larger than the small-upload threshold that carries none is answered with one confirmation covering the file list and the price together. A smaller post goes straight through."New value: +"Optional: the id of an upload approval the account owner already confirmed. A large post without one is answered with a confirmation covering the files and the price."
  2. Changed1 schema field changed
    • changedInput schema / properties / uploadGrant / description
      Previous value: -"The grant id `preview_upload` returned, once the account owner has confirmed it. Required only for a post larger than the small-upload threshold; a smaller one goes straight through."New value: +"The id of an upload approval the account owner has already confirmed. Optional: a post larger than the small-upload threshold that carries none is answered with one confirmation covering the file list and the price together. A smaller post goes straight through."
  3. Added

TDQS

A4.9/5.0
Behavior5/5

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

The description fully discloses that the tool costs money, requires human confirmation, saves reports as private, and has a multi-call confirmation workflow. It also clearly explains that prices are re-quoted if changed and never charged without owner confirmation, matching the non-read-only, non-idempotent annotation.

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?

The description is dense and well-structured but somewhat repetitive, especially around cost and the three-call flow, which are explained twice. The key operational details are front-loaded and important, but trimming redundant payment explanations would improve conciseness.

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?

Given the complexity of the payment and confirmation workflow and the absence of an output schema, the description provides sufficient context: it explains the three-call sequence, key requirement, price confirmation, fullScan option, privacy of reports, and what the caller receives. No critical operational detail seems missing.

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

Parameters5/5

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

The schema already covers all parameters, and the description adds valuable semantics beyond the schema, including sanitization of the name, path restrictions, rejection of encodings other than utf8, the cap on files, and the exact role of confirmedCost and authorization in the payment flow.

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 title and description clearly state the tool performs a paid AI audit of posted source files, specifically for projects without a GitHub remote. It distinguishes itself from repo-based or scanning siblings by emphasizing 'no GitHub repo' and 'source files, not build output.'

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 gives concrete guidance on when to use the tool, what file types are acceptable, the need for an API key, the three-call payment flow, and the optional fullScan tier. It also explicitly instructs users to omit confirmedCost on the first call and echo back the exact quoted cost afterward.

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