Skip to main content
Glama

get_schema

Read-only

Look up field names, descriptions, units and band values. Search rather than pulling everything (~230 KB): search="bull flag", category=patterns, level=market. Names are []; bands end in a category word (_zone, _state, _trend), raw numbers in a unit (_pct, _ratio, _usd). Every band (tracked: true) also has _prev, _periods, _flips_recent_count, _flips_lookback and _stability, usable as fields and filters; lookups omit those rows unless markers=true. Over 25 matches lists names only: search again by exact name for a description.

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": "get_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNoticker = per-asset fields; market = market_*/macro_*; model = model_* (TickerDB's trading models).
appendNoAdd rows to an existing store_as table instead of replacing it.
searchNoWords that must all appear in name, category or description.
compactNoName, type, values and description only.
markersNoInclude change-marker fields.
categoryNoComma-separated, e.g. patterns,volume.
store_asNoTable name: store rows in SQLite, return only a summary. Read with query_data.

Output Schema

NameRequiredDescriptionDefault
dataNoThe tool's result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / append
      Added value: +{
      +  "description": "Add rows to an existing store_as table instead of replacing it.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / category
      Added value: +{
      +  "description": "Comma-separated, e.g. patterns,volume.",
      +  "type": "string"
      +}
    • addedInput schema / properties / compact
      Added value: +{
      +  "description": "Name, type, values and description only.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / level
      Added value: +{
      +  "description": "ticker = per-asset fields; market = market_*/macro_*; model = model_* (TickerDB's trading models).",
      +  "enum": [
      +    "ticker",
      +    "market",
      +    "model"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / markers
      Added value: +{
      +  "description": "Include change-marker fields.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / search
      Added value: +{
      +  "description": "Words that must all appear in name, category or description.",
      +  "type": "string"
      +}
    • addedInput schema / properties / store_as
      Added value: +{
      +  "description": "Table name: store rows in SQLite, return only a summary. Read with query_data.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / data / description
      Previous value: -"The TickerDB API response payload for this tool call."New value: +"The tool's result."
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuinely useful behavior beyond them: approximate payload size, the over-25-match truncation to names only, and that band sub-rows are omitted unless markers=true. It is strong on response shape but silent on rate limits or auth.

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?

Dense but front-loaded: purpose first, then the size warning and search strategy, then naming semantics, then truncation behavior. No filler, though the naming-convention sentences are terse enough that an agent must parse them carefully.

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?

Given an output schema exists, the description needn't explain return values, and it still documents payload size, truncation and marker behavior. It leaves the store_as/append and compact semantics to the schema, which is acceptable at 100% coverage.

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%, so the baseline is 3; the description earns more by showing realistic values for search/category/level and by explaining the naming convention (<group>_<name>[_<unit>], band suffixes _zone/_state/_trend, unit suffixes _pct/_ratio/_usd) that lets an agent construct exact-name queries after truncation.

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?

Opens with a specific verb+resource: look up field names, descriptions, units and band values from the schema catalog. The domain is unmistakable (field metadata, not data values), though it never names a sibling such as search_tools or query_data to draw the boundary explicitly.

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?

Gives concrete when-to guidance: prefer targeted search over the ~230 KB full pull, with worked examples (search="bull flag", category=patterns, level=market) and a recovery path when over 25 matches return names only. It stops short of naming alternative tools or stating 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.