Skip to main content
Glama

ASI.EXPRESS

list_operations

Read-onlyIdempotent

List every fixed operation run_capability can run (public data: exchange rates, earthquakes, public holidays, weather, country statistics, Bible verses; computed: units, time zones, dates, calendars, percentages, interest, loans, VAT, bills, trips, sun and moon, cooking, arithmetic), each with its inputs (name, required, pattern, default, example) and a ready one-step recipe, plus chained recipes that join operations (e.g. convert an amount between currencies: exchange rate, then amount x rate). Optional: operation (one id) or kind (data, computed, chained). Nothing is stored or run. Read-only; no model is used.

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_operations"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
operationNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety bar is low; the description nonetheless adds 'Nothing is stored or run. Read-only; no model is used,' which clarifies cost and side-effect profile. It also previews the payload shape (inputs with name/required/pattern/default/example, plus a ready recipe and chained recipes), though some of that overlaps the output schema.

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?

The core statement and constraints are front-loaded, and the long category parenthetical earns its length by signaling coverage an agent would otherwise have to probe for. The sentence is dense and comma-heavy, but no clause is pure filler.

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?

An output schema exists, so return values need not be spelled out, and the description still covers behavior, filters, and scope. The remaining gap is routing guidance against other discovery siblings, which would matter for a zero-required-param listing tool.

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 carries the burden and does so: 'operation (one id)' and 'kind (data, computed, chained)' are both named, and the earlier enumeration gives concrete meaning to each kind value. It stops short of noting that the two filters are alternatives rather than combinable, or what happens on an unknown id.

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?

Specific verb plus resource: 'List every fixed operation run_capability can run,' and it names the sibling that executes them. The parenthetical taxonomy (public data vs computed vs chained) tells an agent exactly what domain coverage to expect 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 Guidelines4/5

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

The description establishes the discovery-then-execute relationship with run_capability and explains that the optional filters narrow the listing by id or by kind. It never states an explicit exclusion or names a competing discovery tool, so the when-not is left implicit.

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