Skip to main content
Glama

tare_receipt

Read-only

Get cost per commit before and after Tare's fixes, shown as a 90% range or a clear 'not enough data yet' notice.

Instructions

Cost per commit before and after Tare's fixes were installed, with a 90% range, or a plain 'not enough data yet'.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, and the description adds genuine value by disclosing the confidence interval and the 'not enough data yet' gating condition. It does not state the aggregation window, the scope the metric covers, or whether results are cached, which leaves real gaps for a zero-parameter report.

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?

One sentence carries the metric, the comparison, the confidence interval, and the fallback case with no filler. The return contract is front-loaded exactly where an agent needs it.

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?

With no parameters and no output schema, the description must carry the whole burden, and it covers the shape of the result and the empty case. It omits the time window and the scope over which cost per commit is computed, which an agent would need to interpret the number.

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?

The schema has zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly does not invent parameter-like scoping that the schema does not support.

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?

The description names a specific metric: cost per commit before and after Tare's fixes, delivered as a point estimate with a 90% range. It is clear what the tool yields, but there is no verb framing and no differentiation from siblings like tare_wrapped or tare_cache.

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 preconditions, and no reference to alternatives such as tare_wrapped for a different summary view. The only contextual note is the insufficient-data fallback, which describes behavior rather than when an agent should call this.

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