Skip to main content
Glama

nittim

by com.nittim
OverviewDiscussionsAdmin

Estimate an Audit's Price — No Upload Required

estimate_audit
Read-onlyIdempotent

Price an audit before buying one: give a GitHub repository URL, or a manifest of paths and byte sizes — no file content, nothing uploaded — and get the tier (Audit or Full Audit), the pass count and the exact price. No account or key is needed: it never charges, runs no audit, calls no model and stores nothing. Signed in it also returns your credit balance and whether an unspent Audit covers the run; a guest quote omits both. fullScan: true prices Full Audit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filesNoA manifest of paths and sizes only, in place of `repoUrl` — the same set you would post. Over the cap the answer names it and how to trim. Send one or the other.
repoUrlNoGitHub repository URL or owner/repo. Mutually exclusive with `files` — send one.
fullScanNoPrice Full Audit (every eligible file, or a refusal with the reason when the selection is too large) instead of the default Audit.
githubTokenNoOptional GitHub personal access token (read-only) for a private repo.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / files / description
      Previous value: -"A manifest of paths and sizes only, in place of repoUrl — the same set you would post for a source-based audit. Sending more than 1000 entries is not a schema error — the answer names the cap and how to trim to it. Mutually exclusive with `repoUrl` — send exactly one."New value: +"A manifest of paths and sizes only, in place of `repoUrl` — the same set you would post. Over the cap the answer names it and how to trim. Send one or the other."
    • changedInput schema / properties / files / items / properties / bytes / description
      Previous value: -"The file's byte size. No `content` field exists on this shape — nothing is uploaded to ask a price."New value: +"The file's byte size. This shape has no `content` — nothing is uploaded."
    • changedInput schema / properties / fullScan / description
      Previous value: -"Price a Full Audit run (reads every eligible file, or refuses with the reason if the selection is too large to sell that way) instead of the default Audit (a fast, sampled pass)."New value: +"Price Full Audit (every eligible file, or a refusal with the reason when the selection is too large) instead of the default Audit."
    • changedInput schema / properties / repoUrl / description
      Previous value: -"GitHub repository URL or owner/repo string, e.g. https://github.com/owner/repo or owner/repo. Mutually exclusive with `files` — send exactly one."New value: +"GitHub repository URL or owner/repo. Mutually exclusive with `files` — send one."
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

The description explicitly discloses that no charge occurs, no audit runs, no model is called, and nothing is stored. It also explains the difference for signed-in users (credit balance and coverage) and what happens over the cap, going well beyond the readOnlyHint 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 front-loaded with the main purpose and uses compact sentences. There is some repetition of the 'no upload' theme across the title and description, but it is not excessive and reinforces a key differentiator.

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 there is no output schema, the description sufficiently describes what the caller will receive: tier, pass count, exact price, credit balance, coverage, and refusal reason when applicable. It also covers input constraints and error-trimming guidance, making the tool well-rounded for an agent.

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 input schema is fully described: files are a manifest of paths and sizes only, repoUrl is mutually exclusive with files, fullScan switches to Full Audit pricing, and githubToken is optional and read-only. The description adds practical details such as 'Over the cap the answer names it and how to trim.'

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: 'Price an audit before buying one.' It also distinguishes itself from audit/upload tools by emphasizing 'no file content, nothing uploaded' and 'never charges, runs no audit, calls no model and stores nothing.'

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?

It explains exactly when to use the tool: when you need a price estimate before purchasing an audit, and it clarifies the two input modes (repo URL or manifest), the optional token, and the fullScan flag. The 'before buying one' framing and 'no upload' emphasis naturally guide against using audit or upload siblings.

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