Skip to main content
Glama

Find Series

find_series
Read-onlyIdempotent

Browse series with structured filters. Useful when you know the provider+dataset and want to enumerate series by dimensions. If a filter matches nothing, the response lists the dimension codes the dataset actually accepts.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dataset": "EXR",
      "provider": "ECB",
      "dimensions": {
        "FREQ": "M"
      }
    },
    "name": "find_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1-1000 (default 100)
offsetNo0-based offset
datasetYesDataset code
providerYesProvider code
dimensionsNoOptional dimension filter map. A value may be one code or a list of codes to OR together, e.g. {"FREQ":"M"} or {"FREQ":["M","Q"],"CURRENCY":["USD","GBP"]}.
observationsNoInclude observations (default false to save bandwidth)

Output Schema

NameRequiredDescriptionDefault
limitNoLimit applied
offsetNoOffset applied
seriesNoSeries matching dimension filters
total_countNoTotal series count

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedOutput schema / properties / series / items
      Removed value: -{
      -  "properties": {
      -    "dimensions": {
      -      "additionalProperties": {
      -        "type": "string"
      -      },
      -      "description": "Dimension values for series",
      -      "type": "object"
      -    },
      -    "name": {
      -      "description": "Series name",
      -      "type": "string"
      -    },
      -    "observations": {
      -      "description": "Time series data points (if requested)",
      -      "items": {
      -        "properties": {
      -          "date": {
      -            "description": "Observation date",
      -            "type": "string"
      -          },
      -          "value": {
      -            "description": "Observed value or null",
      -            "type": [
      -              "number",
      -              "null"
      -            ]
      -          }
      -        },
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    "series_code": {
      -      "description": "Series code",
      -      "type": "string"
      -    }
      -  },
      -  "type": "object"
      -}
    • addedOutput schema / properties / series / properties
      Added value: +{
      +  "docs": {
      +    "items": {
      +      "properties": {
      +        "dataset_code": {
      +          "type": "string"
      +        },
      +        "dataset_name": {
      +          "type": "string"
      +        },
      +        "dimensions": {
      +          "properties": {
      +            "CURRENCY": {
      +              "type": "string"
      +            },
      +            "CURRENCY_DENOM": {
      +              "type": "string"
      +            },
      +            "EXR_SUFFIX": {
      +              "type": "string"
      +            },
      +            "EXR_TYPE": {
      +              "type": "string"
      +            },
      +            "FREQ": {
      +              "type": "string"
      +            }
      +          },
      +          "type": "object"
      +        },
      +        "indexed_at": {
      +          "type": "string"
      +        },
      +        "provider_code": {
      +          "type": "string"
      +        },
      +        "series_code": {
      +          "type": "string"
      +        },
      +        "series_name": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "type": "array"
      +  },
      +  "limit": {
      +    "type": "number"
      +  },
      +  "num_found": {
      +    "type": "number"
      +  },
      +  "offset": {
      +    "type": "number"
      +  }
      +}
    • changedOutput schema / properties / series / type
      Previous value: -"array"New value: +"object"
  2. Changed4 schema fields changed
    • changedInput schema / examples
      Previous value: -[
      -  {
      -    "dataset": "EXR",
      -    "dimensions": {
      -      "FREQ": "M"
      -    },
      -    "provider": "ECB"
      -  },
      -  {
      -    "dataset": "UNE_RT_A",
      -    "dimensions": {
      -      "COUNTRY": "DE",
      -      "SEX": "T"
      -    },
      -    "observations": true,
      -    "provider": "EUROSTAT"
      -  }
      -]New value: +[
      +  {
      +    "dataset": "EXR",
      +    "dimensions": {
      +      "FREQ": "M"
      +    },
      +    "provider": "ECB"
      +  },
      +  {
      +    "dataset": "une_rt_a",
      +    "dimensions": {
      +      "geo": "DE",
      +      "sex": "T"
      +    },
      +    "limit": 3,
      +    "provider": "EUROSTAT"
      +  }
      +]
    • addedInput schema / properties / dimensions / additionalProperties / oneOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  }
      +]
    • removedInput schema / properties / dimensions / additionalProperties / type
      Removed value: -"string"
    • changedInput schema / properties / dimensions / description
      Previous value: -"Optional dimension filter map, e.g. {\"FREQ\":\"A\",\"COUNTRY\":\"DE\"}"New value: +"Optional dimension filter map. A value may be one code or a list of codes to OR together, e.g. {\"FREQ\":\"M\"} or {\"FREQ\":[\"M\",\"Q\"],\"CURRENCY\":[\"USD\",\"GBP\"]}."
  3. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "dataset": "EXR",
      +    "dimensions": {
      +      "FREQ": "M"
      +    },
      +    "provider": "ECB"
      +  },
      +  {
      +    "dataset": "UNE_RT_A",
      +    "dimensions": {
      +      "COUNTRY": "DE",
      +      "SEX": "T"
      +    },
      +    "observations": true,
      +    "provider": "EUROSTAT"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "limit": {
      +      "description": "Limit applied",
      +      "type": "number"
      +    },
      +    "offset": {
      +      "description": "Offset applied",
      +      "type": "number"
      +    },
      +    "series": {
      +      "description": "Series matching dimension filters",
      +      "items": {
      +        "properties": {
      +          "dimensions": {
      +            "additionalProperties": {
      +              "type": "string"
      +            },
      +            "description": "Dimension values for series",
      +            "type": "object"
      +          },
      +          "name": {
      +            "description": "Series name",
      +            "type": "string"
      +          },
      +          "observations": {
      +            "description": "Time series data points (if requested)",
      +            "items": {
      +              "properties": {
      +                "date": {
      +                  "description": "Observation date",
      +                  "type": "string"
      +                },
      +                "value": {
      +                  "description": "Observed value or null",
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                }
      +              },
      +              "type": "object"
      +            },
      +            "type": "array"
      +          },
      +          "series_code": {
      +            "description": "Series code",
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "total_count": {
      +      "description": "Total series count",
      +      "type": "number"
      +    }
      +  },
      +  "type": "object"
      +}
  4. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds a genuinely useful behavioral trait beyond that: when a filter matches nothing, the response returns the dimension codes the dataset accepts, turning an empty result into actionable guidance. It says nothing about pagination limits or result size, so the added value is real but limited.

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?

Three short sentences, front-loaded with the action and followed by the usage condition and the empty-result behavior. No redundant phrasing; the only minor weakness is that the empty-result sentence could be tied more explicitly to the filter parameter.

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?

An output schema exists, so return values need not be explained, and the description covers the notable edge case of a no-match filter. For a six-parameter tool with a nested dimensions object, this is close to complete, with pagination behavior the only notable omission.

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 description coverage is 100% and the dimension map's OR-semantics are already spelled out in the schema itself. The description adds no syntax, default, or format detail beyond that, so the schema carries the load and baseline 3 applies.

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 and resource ("Browse series") and scopes it to a known provider+dataset, which is more than a restatement of the name. It does not explicitly name a sibling such as dbnomics_get_series to distinguish single-series retrieval from enumeration, so it stops short of a 5.

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 a clear selection condition: use when you already know the provider+dataset and want to enumerate series via dimensions. It implies the alternative (search/discovery) without naming one and gives no explicit when-not guidance, so it is clear context rather than full routing guidance.

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.