Skip to main content
Glama

Explain a term or setting

acubic_explain
Read-onlyIdempotent

Explains one investing term or Acubic setting in plain language (a metric such as P/E or maximum drawdown, a filter, ranking or weighting method, risk level, rebalance or backtest term): its meaning, how Acubic uses it, default, caveats and its page. Use it whenever the user asks what a term means, so the answer matches how Acubic computes it. It does not say what a person should choose. For articles, pricing or the FAQ use acubic_search_knowledge.

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": {
      "topic": "<topic>"
    },
    "name": "acubic_explain"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoLimit to one kind of term.
topicYesA term or option id, e.g. 'P/E ratio', 'pe', 'cap_rank_10', 'walk-forward'.
localeNoThe language of this conversation.
response_formatNoconcise

Output Schema

NameRequiredDescriptionDefault
errorNo
matchesNo
truncatedNo
suggestionsNoClose terms when nothing matches exactly.
content_localeNoLanguage of the wording: en for now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: the response shape (meaning, how Acubic uses the term, default, caveats, page link) and the boundary that it will not give personal recommendation advice. It stops short of describing depth differences between the concise and detailed response modes.

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?

Front-loaded with the action and scope, then guidance, then the exclusion — good ordering with no filler sentences. The long parenthetical enumeration of term types makes the first sentence dense, but each clause carries routing or scoping information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 need not explain return values, and it doesn't over-explain. Combined with annotations covering safety and idempotency, the definition gives an agent everything needed to decide to call it, what to pass, and when to route elsewhere.

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 coverage is 75% and each parameter already carries a description and enum values, so the schema does most of the work. The description reinforces that only one term is explained at a time and its term-type list loosely mirrors the `kind` enum, but it says nothing about `locale`, `response_format`, or what happens when `kind` mismatches `topic`. Baseline 3 is appropriate.

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?

States a specific verb ("Explains") and a bounded resource ("one investing term or Acubic setting"), then enumerates the term families it covers (metric, filter, ranking/weighting method, risk level, rebalance, backtest term) and names the sibling that handles other content. An agent can distinguish it from acubic_search_knowledge 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 Guidelines5/5

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

Gives an explicit trigger ("Use it whenever the user asks what a term means"), a rationale (so answers match Acubic's computation), an explicit non-goal ("does not say what a person should choose"), and a routing rule to an alternative ("For articles, pricing or the FAQ use acubic_search_knowledge"). Both when-to-use and when-not-to-use are covered.

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