Skip to main content
Glama

Invoices to clients

dosai_list_invoices
Read-onlyIdempotent

Payment requests the business sent to its clients (Kaspi): amount, status, when paid. Viewing only: issuing, cancelling and refunding stay in the cabinet. Owner or project admin.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>"
    },
    "name": "dosai_list_invoices"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, default 1.
statusNoFilter by status, as shown in the cabinet.
project_idYesFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed1 schema field changed
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the explicit redirection of create/cancel/refund actions to the cabinet, and the access constraint 'Owner or project admin', which is a permission requirement the annotations do not convey.

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

Conciseness5/5

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

Two compact sentences plus a terse access fragment; the resource definition leads, the read-only boundary follows, and nothing is redundant. No filler, no restatement of the title.

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 list tool with three fully documented parameters and no output schema, the definition covers what an agent needs: what is listed, that it is view-only, and who may call it. The only minor gap is that it does not hint at result shape or pagination behavior beyond the page parameter's own schema entry.

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%, with page, status and project_id all documented inline, so the schema does the heavy lifting. The description's mentions of amount, status and 'when paid' describe the returned data rather than adding meaning to the status filter or page semantics, so a baseline score is appropriate.

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?

The description names a concrete resource with its domain qualifier ('Payment requests the business sent to its clients (Kaspi)') and enumerates the fields it reports (amount, status, when paid), which is far more specific than the bare tool name. It does not explicitly contrast itself with neighboring list tools, but the resource is distinct enough that an agent can identify it without opening the schema.

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

Usage Guidelines3/5

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

The definition states a useful boundary — 'Viewing only: issuing, cancelling and refunding stay in the cabinet' — which tells the agent not to reach for this tool when a write is requested. However, it gives no guidance on when to prefer this over other listings or how to narrow results (e.g. status filtering as a strategy); the project_id provenance hint appears only in the schema.

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