Israel Statistics MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_index_topicsC | Get index topics from Israel Statistics API |
| get_index_dataC | Get index data from Israel Statistics API |
| get_catalog_chaptersC | Get list of index chapters from Israel Statistics API |
| get_chapter_topicsC | Get topics for a specific chapter from Israel Statistics API |
| get_subject_codesB | Get index codes for a specific subject/topic from Israel Statistics API |
| get_index_calculatorC | Calculate price linkage using Israel Statistics API index calculator |
| get_main_indicesC | Get main indices by different bases from Israel Statistics API |
| get_main_indices_by_periodC | Get main indices filtered by period from Israel Statistics API |
| get_all_indicesC | Get all indices by different bases with optional chapter filtering from Israel Statistics API |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools have distinct purposes, such as get_catalog_chapters for chapters and get_index_data for index data, but there is some overlap between get_all_indices and get_main_indices that could cause confusion. The descriptions help clarify, but an agent might need to infer the difference between 'all indices' and 'main indices'.
All tool names follow a consistent verb_noun pattern with 'get_' prefix, such as get_all_indices and get_index_data. There are no deviations in naming style, making the set predictable and easy to parse.
With 9 tools, the count is well-scoped for a statistics API server, covering various aspects like indices, chapters, topics, and calculations. Each tool appears to serve a specific function without redundancy, fitting the domain appropriately.
The tool set provides comprehensive coverage for querying and calculating statistics, including data retrieval, catalog browsing, and calculations. A minor gap might be the lack of update or delete operations, but this is reasonable for a read-only statistics API, and agents can work around this limitation.