Skip to main content
Glama

Paid Search Bid Ceiling

bpj_paid_search_bid_ceiling
Read-onlyIdempotent

Derive the maximum average CPC from allowed cost per retained order, click conversion and order validity.

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": {
      "allowance": "<allowance>",
      "conversion": "<conversion>",
      "valid": "<valid>"
    },
    "name": "bpj_paid_search_bid_ceiling"
  }
}

Input Schema

NameRequiredDescriptionDefault
validYes
allowanceYes
conversionYes

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 readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description confirms the pure-derivation nature but discloses nothing about the formula, rounding, unit handling, or error behavior for zero/edge inputs.

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 with no wasted words. It is slightly compressed to the point of ambiguity about how the three inputs combine, but structurally efficient.

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-parameter calculator with no output schema, the description should state what is returned (e.g., a single CPC value) and the computation logic. It omits both, though the annotations leave little behavioral risk unexplained.

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%, with only titles carrying units (allowance in currency per order, conversion and valid in %). The description maps each of the three parameters to a role but adds no format, typical range, or formula linking them, so it only partially compensates for the coverage gap.

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?

States a specific verb ('derive') and a specific output ('maximum average CPC'), plus the three inputs it consumes. An agent can tell it computes a bid ceiling rather than a budget cap, but the description does not name a sibling to contrast with.

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 explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as budget- or frequency-cap ceiling tools. Usage is only implied by the fact that it is a derivation from three inputs.

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.