Skip to main content
Glama

Sponsorship Flat Rate Benchmark

bpj_sponsorship_flat_rate_benchmark
Read-onlyIdempotent

Compare a flat sponsorship quote against a benchmark CPM and calculate guaranteed impressions needed to match the benchmark.

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": {
      "fee": "<fee>",
      "impressions": "<impressions>",
      "cpm": "<cpm>"
    },
    "name": "bpj_sponsorship_flat_rate_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpmYes
feeYes
impressionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, which tells the agent this is a pure, side-effect-free computation. The description confirms the comparative/calculative nature but adds nothing about rounding, currency assumptions, or what the comparison produces. With annotations carrying the safety profile, a 3 is appropriate.

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 front-loaded sentence that states the comparison and the derived metric with no filler. The second clause is slightly ambiguous, but nothing is wasted.

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, so the description should say what comes back (implied CPM vs benchmark, delta, impressions needed, or all of them) and in what units. For a three-parameter calculator with a required impressions input and a claimed impressions output, this omission leaves genuine ambiguity an agent cannot resolve from structured fields.

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

Parameters2/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 parameter meaning, and it largely restates the schema titles (flat quote, benchmark CPM, guaranteed impressions). It never gives the formula or unit assumptions (e.g. currency for fee, per-mille basis for cpm), and it is ambiguous about whether 'impressions' is an input or the computed result even though the schema marks it required.

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 action (compare a flat sponsorship quote against a benchmark CPM) and a specific derived quantity (impressions needed to match the benchmark), so the agent knows this is a sponsorship-rate benchmarking calculator. It does not differentiate against any sibling tool, but the verb+resource pairing is unambiguous.

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 or when-not-to-use guidance at all, and no alternative tool is named. The agent must infer from the name alone that this is the flat-rate sponsorship variant rather than one of the many other benchmark calculators in the family.

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.