Skip to main content
Glama

SofortFax (KI-Fax-Credits)

Faxpreis abfragen

get_fax_price
Read-onlyIdempotent

Prüft, ob eine Faxnummer erlaubt ist. Mit KI-Credits kostet jedes Fax 1 Credit (bis 100 Seiten).

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_fax_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesNoSeitenzahl (optional, 1–100).
fax_numberNoFaxnummer des Empfängers (optional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / pages / description
      Previous value: -"Seitenzahl (optional, 1–40)."New value: +"Seitenzahl (optional, 1–100)."
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real context beyond that: the fixed cost of 1 credit per fax and the 100-page ceiling, plus the fact that the call validates the recipient number. It does not say what happens with a disallowed number or what the response contains.

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?

Two short sentences with no filler, and the cost constraint is stated compactly. The ordering is slightly off — the permission check precedes the pricing fact even though the tool name emphasizes price — but nothing is wasted.

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?

Annotations carry the safety profile and the schema fully documents both optional parameters, so the definition is close to sufficient for a simple lookup. It still leaves unclear what the tool returns (price only, boolean permission, or both) for a tool with no output schema.

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 coverage is 100%, with both optional parameters documented in the schema, so the baseline is 3. The description only reinforces the 100-page bound already in the schema and implies fax_number drives the permission check; it adds no format or edge-case detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says it checks whether a fax number is permitted and states the price model (1 credit per fax, up to 100 pages), but the tool name and title promise a price lookup while the text leads with a permission check. An agent can infer the combined intent (validate + price), yet the primary action is not stated with a clean verb+resource.

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?

No guidance on when to call this versus siblings such as send_fax or get_account_balance, and no preconditions (e.g., call before sending to avoid failed sends). The cost statement is informational rather than usage direction.

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.

Resources