Skip to main content
Glama
jkbngb

agentic-firmenbuch

by jkbngb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

My API usage

get_my_usage
Read-onlyIdempotent

Check your own API key's call count and compute units per tool for today, yesterday, month-to-date, last 30 days or all time, plus credits and quota status.

Instructions

Your own API-key usage: call count and weighted compute-units, per tool. Read-only.

    Parameter:
    - window (optional, default "today"): one of "today", "yesterday", "month_to_date",
      "last_30_days", "all".

    Returns only the calling key's own usage (totals + per-tool breakdown) for that window,
    plus `plan` (the plan in force). Credit-metered accounts additionally get `credits_used`
    (credits charged in the window), `credits_remaining` (current balance) and the `credits`
    block with per-lot detail — for them, Credits are the billing unit (calls/compute_units
    are internal telemetry; failed attempts cost 0). Free-plan keys use this to check their
    consumption against the monthly free quotas. Never another user's data and never the
    e-mail behind the key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
windowNotoday

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent/non-destructive, yet the description adds substantial behavior beyond them: failed attempts cost 0, credits are the billing unit for metered accounts while calls/compute_units are internal telemetry, and the response never leaks another user's data or the e-mail behind the key.

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 with the core purpose and scope in the first sentence, with the parameter and return details following. Some return-field detail is verbose given an output schema exists, but it is organized and each sentence carries information.

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?

For a single optional parameter read-only tool with an output schema, the description supplies the enum values, default, scope guarantees, and billing semantics. Nothing needed to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the enum list is absent from the schema, so the description fully compensates by enumerating all five allowed window values and restating the default 'today'. Without this text an agent could not know the valid inputs.

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+resource ('Your own API-key usage: call count and weighted compute-units, per tool') and explicitly frames the scope as the calling key only. This is trivially distinguishable from every sibling, which are all company/person/document tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete usage context: free-plan keys use it to check consumption against monthly free quotas, and credit-metered accounts use it for balance/billing detail. It does not name explicit alternatives or when-not-to-use, but the sibling set makes mis-selection unlikely.

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

Deploy Server

Other Tools