Skip to main content
Glama

Explain a market term

explain_term
Read-onlyIdempotent

Look up a trading or market term (for example 'stop-limit order', 'bid-ask spread', 'yield curve') in ATLAS Explain's plain-language glossary. Education 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": {
      "term": "<term>"
    },
    "name": "explain_term"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesThe term or phrase to look up.

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 safety profile is fully covered by structured data. The description adds only the framing that results come from a curated plain-language glossary and that the content is educational; it says nothing about coverage limits, unknown-term behavior, or response shape.

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?

Two sentences, no filler, with the action and source front-loaded and the scope caveat trailing. Every clause carries information an agent can act on.

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?

For a one-parameter, read-only lookup with complete annotations and a fully described schema, this is close to sufficient. The only meaningful omission is any indication of what happens for an unrecognized term, which would help an agent decide whether to retry with a different phrasing.

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 100% and the single parameter is already documented as "The term or phrase to look up." The description still earns credit above baseline by supplying example values ("stop-limit order", "bid-ask spread", "yield curve"), which clarify the expected granularity and domain of acceptable input.

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?

Names a specific verb and resource ("look up a trading or market term") and pins down the source ("ATLAS Explain's plain-language glossary") with three concrete example terms. It does not, however, distinguish itself from the sibling browse_glossary, so an agent cannot tell from this text alone whether to look a term up directly or browse the glossary.

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?

"Education only" sets a scope boundary that implies this is for definitional questions rather than pricing or news lookups, which weakly separates it from siblings like crypto_prices or todays_headlines. There is no explicit when-to-use or when-not-to-use statement, and the most plausible alternative (browse_glossary) is never mentioned.

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.