Skip to main content
Glama

SBChart2.0 MCP

by kr.co.softbowl

searchSBChartAPI

Search SBChart2.0 chart API and option documentation by keyword. Returns matching entries with name, section, summary, and syntax. Start here to find which option or chart type fits, then call getSBChartAPIDetail for full details or getSBChartExample for code. ⚠️ SBChart2.0 코드/샘플 생성 시 서버 공통지침(표준 골격에서 출발 · chartConfig 리터럴 나열 · 요청 기능만 최소 적용) 준수 — 상세는 서버 instructions 참고.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return. Default 5.
queryYesKeyword to search: a chart type, option, or feature (e.g. 'bar', 'tooltip', 'gantt', 'axis').
sectionNoOptionally restrict results to one section.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of results to return. Default 5."
    • changedInput schema / properties / query / description
      Previous value: -"Search keyword"New value: +"Keyword to search: a chart type, option, or feature (e.g. 'bar', 'tooltip', 'gantt', 'axis')."
    • changedInput schema / properties / section / description
      Previous value: -"Filter by section"New value: +"Optionally restrict results to one section."
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations provided, but description suggests read-only search and lists return fields. Does not explicitly state idempotency, safety, or side-effect absence, leaving some ambiguity.

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?

Reasonably concise with main purpose upfront. The additional Korean warning about code generation guidelines adds minor clutter but does not severely hinder readability.

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 no output schema, description adequately specifies return fields. Lacks details on pagination or rate limits, but for a simple search tool with explicit sibling links, it is largely complete.

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 baseline is 3. Description adds context about keyword examples and the overall search purpose but does not provide deeper semantics beyond the schema.

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?

Clearly states it searches SBChart2.0 documentation by keyword, returns specific fields, and distinguishes from siblings by recommending where to start.

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?

Explicitly says 'Start here' and suggests subsequent tools (getSBChartAPIDetail, getSBChartExample), providing clear when-to-use guidance. Lacks explicit when-not-to-use, but differentiation is sufficient.

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

All SBChart2.0 MCP 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/5.0
Disambiguation5/5

Each tool has a distinct, non-overlapping purpose: search for APIs, browse by section, retrieve full documentation, and get code examples. No ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using CamelCase with the 'SBChart' prefix (e.g., searchSBChartAPI, getSBChartExample). No mixing of conventions.

Tool Count5/5

With 4 tools covering search, browse, detail, and example retrieval, the count is well-scoped for a documentation helper server. Not too few or too many.

Completeness4/5

The tool set covers the main workflows—finding APIs and retrieving documentation/examples. Minor gaps like version info or bulk listing are absent, but core functionality is solid.

Resources