Skip to main content
Glama

Babelii-Diofis Account

Pembelian terjadwal saya

account_schedules
Read-onlyIdempotent

The account's scheduled purchases: label, product, masked destination, recurrence, status and next run. Up to 50 rows; pass next_before_id as before_id for the next page. Read only.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
before_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description still adds real behavioral context: a hard 50-row cap per call and the exact continuation mechanism ('pass next_before_id as before_id for the next page'), which is not derivable from the annotations. It says nothing about ordering or what an empty result means, keeping it below a 5.

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 dense sentences, front-loaded with the resource and returned fields, then pagination, then the read-only note. Every clause carries information, but the paging sentence packs a field-name reference ('next_before_id') that reads a bit cryptically for anyone who has not seen a response yet.

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?

With an output schema present, return shape need not be spelled out, and read-only safety is covered by annotations; the description fills the remaining gaps (page size, cursor chaining, field list). The one unresolved element is how limit interacts with the 50-row cap, which an agent may have to discover by trial.

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

Parameters4/5

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

Schema coverage is 0%, so the description must carry the burden, and it does so for the less obvious parameter: it explains that before_id is a cursor taken from the previous page's next_before_id. 'Up to 50 rows' implicitly communicates the effective limit ceiling, though the limit parameter itself is never named or explained beyond that.

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 states specifically what the tool returns: 'The account's scheduled purchases' followed by an explicit field list (label, product, masked destination, recurrence, status, next run). That is far more concrete than the vague title 'Pembelian terjadwal saya'. It does not, however, differentiate itself from the sibling account_schedule_runs, so an agent must infer the split between schedule definitions and schedule executions.

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 or when-not-to-use guidance and no named alternative, even though account_schedule_runs is a closely related sibling that an agent could easily confuse with this one. The only steering is the pagination instruction, which is operational rather than usage guidance.

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