Skip to main content
Glama

Ask Miss QE (QE Virtual AI Machine)

ask_miss_qe
Read-only

Ask Miss QE, the economic engineer of the OwlChart QE Virtual AI Machine, about the money pipes of one country: central bank, government debt, bond yield, exchange rate, inflation, unemployment and more, each read from the national source. She answers in the language of the question: which pipes drain or flow, what would repair each one and who holds the tap. Every number is checked against the machine. Needs the Miss QE pass; without it the answer is the price and where to buy. Not advice.

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": {
      "country": "<country>",
      "question": "<question>"
    },
    "name": "ask_miss_qe"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesCountry code of the machine: us, eu, es, de, fr, it, gb, jp, cn, au, nz, kr and the rest; GET https://owlchart.com/api/liquidity/countries lists them
questionYesThe question, in any language

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only and open-world behavior, and the description adds important context: a pass is required, the unpurchased answer is a price and purchase location, numbers are checked against the machine, and the output is not advice. It does not cover rate limits or return shape, but it discloses meaningful paywall and safety behavior beyond annotations.

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 purpose is front-loaded with 'Ask Miss QE,' and the description is reasonably compact. The metaphorical phrasing ('money pipes,' 'who holds the tap') adds color but also some verbosity.

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 two-parameter natural-language Q&A tool with full schema coverage and no output schema, the definition covers subject matter, country scoping, authentication behavior, and non-advice status. It leaves the answer format somewhat implicit but is otherwise sufficient for correct invocation.

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 100%, so both parameters are already documented in the schema. The description adds that the tool concerns one country and answers in the language of the question, but does not add format or syntax details beyond the schema baseline.

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 a specific action (ask Miss QE) and a concrete domain (central bank, government debt, bond yield, exchange rate, inflation, unemployment, and more) for one country. It is clear enough to distinguish from generic market tools, though it does not explicitly name when to prefer this over siblings like get_inflation or get_liquidity.

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?

Usage is implied: ask country-level macro/financial plumbing questions, and the tool requires a Miss QE pass. The description does not explicitly compare this with alternatives such as get_inflation or get_liquidity, nor does it state when not to use it.

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