Skip to main content
Glama

SofortFax (KI-Fax-Credits)

Fax-Verlauf

list_fax_history
Read-onlyIdempotent

Listet die letzten Faxe dieses KI-Credits-Keys mit Status.

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

Input Schema

NameRequiredDescriptionDefault
limitNo1–50, Standard 10.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds the useful scoping fact that results are limited to this AI credit key's faxes, but says nothing about ordering, pagination beyond the limit parameter, or how status values are represented.

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 short sentence with the scope and returned field front-loaded and zero filler. It is efficient, though the terseness leaves room for one more routing sentence without becoming bloated.

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 one-parameter, read-only list tool with full schema coverage and no output schema, this is close to sufficient: the agent knows the scope, the result content, and the limit. Missing only ordering guarantees, which is minor for a simple history listing.

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% — the limit parameter's range and default (1–50, Standard 10) are fully documented in the schema. The description adds nothing about the parameter, so the baseline 3 for a single well-documented param applies.

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 ("Listet"), resource ("Faxe") and scope ("dieses KI-Credits-Keys"), plus what is returned ("mit Status"). It implies a recency-ordered list, distinguishing it from the single-item get_fax_status, but never names that sibling to make the split explicit.

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 guidance, no prerequisites, and no mention of the obvious alternative get_fax_status for a single fax. The agent must infer that this tool is the bulk/recent-listing variant purely from the word "letzten".

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