Skip to main content
Glama

ASI.EXPRESS

suggest_capability

Read-onlyIdempotent

Say what you need in a few English keywords. Returns up to 3 ready recipes built from the fixed list of operations (exchange rates, earthquakes, public holidays, weather forecasts, country statistics, and computed ones: unit conversion, time zones, date arithmetic, Hebrew calendar dates, percentages, interest and loan payments), each with its input names. Nothing is stored or run. Read-only; no model is used.

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": {
      "need": "<need>"
    },
    "name": "suggest_capability"
  }
}

Input Schema

NameRequiredDescriptionDefault
needYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety bar is low; the description still adds genuinely new facts: nothing is stored or run, no model is used, and output is capped at 3 recipes. It does not say what happens on ambiguous or unmatched input, which is the one remaining behavioral gap.

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?

The action and output are front-loaded in the first two sentences, then the parenthetical operation list defines scope, and the closing sentence closes the loop on side effects. Every sentence carries information; the enumeration is long but is the actual boundary of what the tool recognizes.

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, the description correctly avoids detailing return structure while still telling the agent the recipes come with input names. The only missing piece is how the returned recipes relate to follow-up siblings like run_capability or propose_capability.

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% with a single required parameter, so the description must carry the meaning — and it does, specifying that 'need' takes a few English keywords rather than a query syntax or an operation ID. That is exactly the guidance needed to fill the field well.

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?

States a specific verb (suggest) and resource (ready recipes) and enumerates the fixed operation families it draws from, so the agent knows exactly what it will get back. It never names or distinguishes itself from plausible siblings like search_capabilities or propose_capability, which sound like they answer a similar need.

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 opening 'Say what you need in a few English keywords' implies the usage context and input style, but there is no explicit when-to-use-when-not guidance and no routing to alternatives such as search_capabilities or get_capability. The agent must infer when this discovery tool is preferable to those siblings.

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