Skip to main content
Glama

Shibui Finance

by finance.shibui.mcp

Load Query Patterns

get_query_patterns
Read-onlyIdempotent

REQUIRED before stock_data_query, 23 SQL patterns prevent timeouts/wrong results

Must be called once per session immediately after get_database_schema. Contains query patterns for time-series selection, return calculations, screening joins, window functions, backtesting, and performance optimization. Time-series queries will timeout or return wrong results without these patterns. After this tool returns, call stock_data_query to execute SQL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate readOnly and idempotent behavior; description adds critical prerequisite context and consequences (timeouts/wrong results) without contradicting 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?

Description is front-loaded with the critical requirement and remains compact. Some redundancy exists ('REQUIRED', 'Must be called', 'without these patterns'), but every sentence contributes value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema and annotations, the description fully covers purpose, prerequisites, sequencing, and failure consequences. It is complete for an agent to invoke correctly.

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?

Tool has no parameters and schema coverage is 100%, so the description need not explain parameters. Baseline 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description explicitly states the tool loads 23 SQL query patterns, identifies it as REQUIRED before stock_data_query, and enumerates pattern categories. This clearly distinguishes it from sibling workflow-loading tools.

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?

Provides explicit sequencing: must be called once per session, immediately after get_database_schema, and before stock_data_query. Does not mention when not to use or alternatives, but the context is strong and specific.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Shibui Finance toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct aspect of stock data workflow: schema discovery, query patterns, raw data access, Excel export, and eight specialized analysis workflows. The load_*_workflow tools are clearly differentiated by domain (earnings, filing, insider, etc.) with explicit usage criteria. There is no real overlap or confusion between tools.

Naming Consistency4/5

Most tools follow a consistent verb_noun snake_case pattern (get_database_schema, get_query_patterns, load_*_workflow, export_to_excel). The only deviation is 'stock_data_query' which places the noun first rather than the verb, but it remains readable and fits the overall naming style. The consistent use of snake_case and descriptive prefixes makes the set predictable.

Tool Count5/5

With 12 tools, the server is well-scoped for its purpose of comprehensive US stock data analysis. Each tool earns its place: two prerequisite/metadata tools, one query executor, one export utility, and eight distinct workflow loaders covering major analysis types. There is no bloat or redundancy.

Completeness5/5

The tool set provides a complete lifecycle for stock data analysis: schema discovery → query patterns → data query → specialized workflows (backtesting, comparison, earnings, filings, fundamentals, insider, screening, technical) and export. It covers all major query types described in the schema tool and leaves no obvious dead ends; agents can handle a wide range of financial questions.

Resources