Skip to main content
Glama

Świadectwo Energetyczne 24

Opcje świadectwa

get_certificate_options
Read-only

Oferta: typy nieruchomości, dla których wystawiamy świadectwo (z ceną bazową brutto PLN), płatny dodatek (wersja papierowa), obsługiwane typy dokumentów i listy dozwolonych wartości (ogrzewanie, CWU, wentylacja, okna, drzwi). Wywołaj jako pierwsze, jeśli użytkownik nie określił typu nieruchomości. Ceny tu są cennikowe — cenę konkretnego zamówienia liczy calculate_certificate_price. Wartości enum podawaj później DOKŁADNIE tak, jak tu wyglądają.

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

Input Schema

NameRequiredDescriptionDefault
property_typeNoZawęź listę typów nieruchomości do jednego typu.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / property_type / description
      Previous value: -"Zawęź listy wartości do jednego typu nieruchomości."New value: +"Zawęź listę typów nieruchomości do jednego typu."
  2. Changed1 schema field changed
    • changedInput schema / properties / property_type / enum
      Previous value: -[
      -  "mieszkanie",
      -  "dom",
      -  "lokal-uzytkowy"
      -]New value: +[
      +  "mieszkanie",
      +  "dom",
      +  "lokal-uzytkowy",
      +  "budynek-nieogrzewany"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / property_type / enum
      Previous value: -[
      -  "mieszkanie",
      -  "dom",
      -  "lokal-uzytkowy",
      -  "garaz"
      -]New value: +[
      +  "mieszkanie",
      +  "dom",
      +  "lokal-uzytkowy"
      +]
  4. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered and nothing is contradicted. The description adds genuinely new context: the returned prices are list prices rather than order-specific, and the enum values returned here must be reused verbatim. It stops short of describing response format/pagination, but with no output schema the payload contents are at least enumerated.

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?

Front-loaded: the payload contents come first, then the calling instructions, then the pricing caveat and enum-verbatim rule. The opening sentence is dense with enumerations but every clause names a distinct part of the response; nothing is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only lookup with annotations covering safety and no output schema, the description carries the return-value burden well by listing the payload categories, and it covers the sibling-routing question. Only the exact response shape/field names remain unspecified, which is a minor gap.

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 100% and the single parameter is documented (narrow the property-type list to one) with its enum listed, so the schema already carries the burden. The description only indirectly implies the parameter's optional, filtering role via the 'if the user hasn't specified a property type' instruction, adding little beyond the schema.

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?

Opens with a specific verb-noun framing ('Oferta') and enumerates exactly what is returned: property types with gross base price, the paid paper-version add-on, supported document types, and allowed-value lists. It also distinguishes itself from the sibling calculate_certificate_price, so an agent can tell the two apart 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?

Gives an explicit trigger ('Wywołaj jako pierwsze, jeśli użytkownik nie określił typu nieruchomości') and names the alternative for pricing ('cenę konkretnego zamówienia liczy calculate_certificate_price'). It also prescribes downstream behavior ('wartości enum podawaj później DOKŁADNIE tak, jak tu wyglądają'), which is uncommonly actionable guidance.

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.