Skip to main content
Glama

SBGrid3.0 MCP

by kr.co.softbowl

searchSBGridAPI

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return. Default 5.
queryYesKeyword to search: a feature, option, or method name (e.g. 'excelExport', 'filter', 'column width', 'row grouping').

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 results to return. Default 5."
    • changedInput schema / properties / query / description
      Previous value: -"Search keyword"New value: +"Keyword to search: a feature, option, or method name (e.g. 'excelExport', 'filter', 'column width', 'row grouping')."
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations; description adds a warning about code generation guidelines, which is behavioral context. Does not disclose rate limits or pagination for results, but the schema covers limit parameter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences plus a relevant warning. Information is front-loaded: purpose first, then usage flow. No wasted words.

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?

For a search tool with 2 parameters and no output schema, the description provides enough context: what to search, what results contain, and how it fits with siblings. Could mention default limit behavior, but limit is documented in schema.

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 does not add significant new detail beyond the schema, but it does contextualize the query as a keyword for API documentation.

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?

Explicitly states it searches SBGrid API documentation by keyword. Distinguishes from siblings by positioning as the starting point and naming getSBGridAPIDetail and getSBGridExample for next steps.

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?

Clearly states to start here and then proceed to sibling tools for details or examples. No explicit when-not-to-use, but the context implies this is for initial exploration.

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