Skip to main content
Glama

SBChart2.0 MCP

by kr.co.softbowl

getSBChartExample

Find runnable SBChart2.0 code examples by feature or use case. Returns example code (data + config) for a chart type or option. Use when you want working sample code rather than the API reference. ⚠️ SBChart2.0 코드/샘플 생성 시 서버 공통지침(표준 골격에서 출발 · chartConfig 리터럴 나열 · 요청 기능만 최소 적용) 준수 — 상세는 서버 instructions 참고.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of examples to return. Default 3.
queryYesChart type, feature, or use case (e.g. 'bar chart', 'donut', 'tooltip', 'sankey').

Schema Changelog

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

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of examples to return. Default 3."
    • changedInput schema / properties / query / description
      Previous value: -"Feature or use case"New value: +"Chart type, feature, or use case (e.g. 'bar chart', 'donut', 'tooltip', 'sankey')."
  2. First observed

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention whether the tool is read-only, requires authentication, has rate limits, or any side effects. The Korean warning about server instructions is vague and not specific to behavioral traits.

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?

The description is two sentences plus a Korean note. The main purpose is front-loaded in the first sentence. The Korean note adds context but is not essential for the core function. Overall concise and well-structured.

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

Completeness2/5

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

Given no output schema, the description vaguely mentions 'example code (data + config)' without specifying format, error handling, or pagination. For a tool with two parameters and sibling tools, it lacks sufficient detail to be fully 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%; both parameters have descriptions in the schema. The description adds no additional meaning beyond the schema (e.g., examples, constraints, types). Baseline of 3 is appropriate.

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?

The description clearly states the tool finds runnable SBChart2.0 code examples by feature/use case, distinguishing it from sibling tools like getSBChartAPIDetail (API details) and listSBChartAPIs (listing APIs). The verb 'Find' and resource 'code examples' are specific.

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?

The description explicitly says 'Use when you want working sample code rather than the API reference', providing clear context for when to use this tool versus siblings. It does not state when not to use or list alternatives explicitly, but the contrast 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