Skip to main content
Glama
Sign In

Aurelmark

by io.github.Ishan73744
OverviewDiscussionsAdmin

Get CBAM certificate price

cbam_get_certificate_price
Read-onlyIdempotent

Returns the latest official CBAM certificate price published by the European Commission (EUR per certificate, one tonne CO2e) with its period, publication date and history. Use it when you only need the price; use cbam_get_default_values for a product's emissions and estimated cost, which already includes this price. No inputs. Output: unit, latest (period, price, published), history[], next expected publication and Commission source links. The Commission publishes quarterly in 2026 and weekly from 2027; we copy each publication, so check latest.published rather than treating it as a live market quote. Terms: read-only; MCP calls are never charged. Without a key, metered routes give 10 successful answers a day free, as short samples (up to 3 records, without file proof, history or paging cursor) where a paid HTTP address exists (unmetered routes are unlimited); errors do not count. On the paid HTTP routes, errors are free, and so are empty answers except a sanctions name search with no match when every loaded list it checks is fresh (lists not loaded yet are named in the answer). An optional API key keeps its prepaid-credit policy. When the free answers run out, the error names the HTTP alternative.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, open-world and non-destructive behavior, so the bar is lower; the description still adds real value by disclosing publication cadence (quarterly 2026, weekly from 2027), that results are copied snapshots rather than live market quotes, and that latest.published should be checked. The quota/metering paragraph adds auth and rate-limit context, though much of it reads as generic boilerplate rather than tool-specific behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are tight and front-loaded, but more than half the text is generic metering boilerplate, including a clause about a sanctions name search with no match that is irrelevant to this tool. That bulk dilutes the useful caveats and makes the definition harder to scan.

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?

With no output schema, the description carries the return-value burden and does so: unit, latest (period, price, published), history[], next expected publication, and source links. Combined with the staleness caveat and the sibling routing, an agent has everything needed to call and interpret it.

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 tool takes no parameters, so the baseline is 4. The description confirms this explicitly with 'No inputs,' which is all that is needed; there is nothing further to clarify.

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?

States a specific verb and resource ('Returns the latest official CBAM certificate price published by the European Commission'), plus units (EUR per certificate, one tonne CO2e) and returned fields (period, publication date, history). It also names the sibling cbam_get_default_values and explains how the two differ, so an agent can disambiguate without opening a schema.

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?

Explicitly gives the selection rule: 'Use it when you only need the price; use cbam_get_default_values for a product's emissions and estimated cost, which already includes this price.' That is a clear when-to-use plus a named alternative and the condition that selects it.

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

All Aurelmark 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