Skip to main content
Glama

Expected cache read latency

bpj_system_cache_latency
Read-onlyIdempotent

Assume all requests pay cache lookup cost and misses also pay backend cost; calculate expected latency.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "hit": "<hit>",
      "lookup": "<lookup>",
      "backend": "<backend>"
    },
    "name": "bpj_system_cache_latency"
  }
}

Input Schema

NameRequiredDescriptionDefault
hitYes
lookupYes
backendYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a read-only, idempotent, non-destructive, closed-world computation, so the safety profile is fully covered. The description does add genuine behavioral context beyond that by disclosing the cost model ('all requests pay cache lookup cost and misses also pay backend cost'), but it stops short of stating the resulting formula or the unit of the returned value.

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?

A single compact sentence with the modeling assumption front-loaded and no filler. The semicolon construction is dense but readable, and nothing in it is redundant with the title.

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 three-required-parameter calculator with no output schema and no annotations gap, the definition covers the core idea but omits the explicit formula and output units, which are the two things an agent most needs to trust the result. Adequate but with clear room to be more complete.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must carry the load, and it partially does: it clarifies that 'hit' is the fraction of requests avoiding the backend and that 'backend' cost applies only on misses, which is meaning the bare schema titles do not convey. However, it leaves 'lookup' semantics and the composition of the three values into a final number implicit, so the coverage gap is only partly closed.

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 verb and output ('calculate expected latency') and ties it to the cache model, so an agent knows this is a latency estimator rather than a measurement or diagnostic tool. It is distinguishable from siblings like bpj_system_single_queue_delay or bpj_system_little_law, though it never explicitly contrasts itself with any of them.

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?

The description gives no when-to-use framing, no preconditions, and no pointer to alternative tools. The only guidance is the embedded modeling assumption, which tells the agent what the tool assumes but not when to pick it over a sibling calculator.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.