Skip to main content
Glama

Babelii-Diofis Account

Riwayat eksekusi pembelian terjadwal

account_schedule_runs
Read-onlyIdempotent

Run history of one of the account's scheduled purchases (schedule_id from account_schedules): when it ran, status, reason and amount. Read only.

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": {
      "schedule_id": "<schedule_id>"
    },
    "name": "account_schedule_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
schedule_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/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 closing 'Read only.' merely restates structured data. What the description does add beyond annotations is the returned content (run time, status, reason, amount), but it omits ordering (are runs newest-first?), the meaning/cap of the default limit of 20, and behavior for an invalid or foreign schedule_id.

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?

A single sentence plus a two-word safety tag, with the resource and the identifier's provenance front-loaded. No filler, no restatement of the title, and every clause carries information.

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?

An output schema exists, so the description need not explain return structure, and read-safety is covered by annotations. For a simple two-parameter history tool the main remaining gaps are ordering of results, limit behavior, and what happens when a schedule has never run — enough that an agent could call it correctly but may misuse the limit or misinterpret an empty response.

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 0%, and with only two parameters the description partially compensates: it explains that schedule_id comes from account_schedules, which is genuine meaning the bare 'Schedule Id' title does not convey. The limit parameter (default 20) gets no explanation at all — no pagination or max-value semantics — so the compensation is incomplete.

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?

The description names the exact resource (run history of one of the account's scheduled purchases) and scopes it to a single schedule, then lists the fields surfaced (when it ran, status, reason, amount). The parenthetical 'schedule_id from account_schedules' ties it to the sibling that supplies the identifier, so an agent can tell this apart from account_schedules without opening either 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?

Usage is implied rather than stated: the reader infers this is only callable after obtaining a schedule_id from account_schedules, and that it is for inspecting past executions rather than altering them. There is no explicit when-not guidance (e.g., don't use for upcoming/unexecuted schedules) and no mention of alternatives such as checking purchase_status for individual transactions.

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