Skip to main content
Glama

SBGrid3.0 MCP

by kr.co.softbowl

getSBGridExample

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of examples to return. Default 3.
queryYesFeature or use case to find examples for (e.g. 'excel export', 'row grouping', 'cell editing').

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: +"Feature or use case to find examples for (e.g. 'excel export', 'row grouping', 'cell editing')."
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

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

No annotations present; description includes a warning about server guidelines for code generation, adding behavioral context, but does not mention read-only nature or other 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?

Two concise sentences plus a supplemental warning; front-loaded with purpose, but the Korean warning may be slightly extraneous.

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?

Adequately covers purpose, usage, and behavioral note for a simple tool with no output schema; minor gap in describing return format.

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%, and description adds context about query being a feature/use case and limit being max number default 3, but does not significantly extend beyond 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?

Describes specific verb 'Find' and resource 'runnable SBGrid3.0 code examples', clearly distinguishing from sibling tools like listSBGridAPIs and searchSBGridAPI.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States 'Use when you want working sample code rather than the API reference', providing explicit guidance on when to use this over alternatives.

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

All SBGrid3.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.3/5.0
Disambiguation5/5

Each tool serves a distinct function: searching, listing categories, getting detailed API documentation, and retrieving example code. There is no overlap in purpose.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., getSBGridAPIDetail, searchSBGridAPI), making the set predictable and easy to navigate.

Tool Count5/5

With 4 tools, the set is well-scoped for exploring API documentation. Each tool earns its place, covering search, browse, detail, and examples without redundancy or gaps.

Completeness5/5

The tools cover the full lifecycle of accessing documentation: search to find, list to browse, get detail for reference, and get example for code. No obvious missing operations.

Resources