Skip to main content
Glama

SvGrid

by com.svgrid

check_svgrid_code

Verify SvGrid code BEFORE handing it to the user. Checks the source against the real exported surface of the current version - prop names, ColumnDef keys, grid API methods, importable symbols and theme files - plus Svelte 5 runes rules, and returns line-numbered diagnostics with the exact replacement for each. Run it on every file you write that uses SvGrid, fix what it reports, and run it again.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYesThe full file contents to check.
filenameNoFile name, used to pick which rules apply. Defaults to "Component.svelte".

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it discloses core behavior: source is compared against the real exported surface plus Svelte 5 runes rules, and it returns line-numbered diagnostics with exact replacements. This makes the tool's behavior and expected output reasonably clear.

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 dense, purposeful sentences: purpose and validation targets are front-loaded, and the workflow instruction is compressed into the final sentence. There is no filler or repetition.

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?

The description tells the agent what the tool does, what it checks, and what kind of output to expect. It could be slightly more explicit about the exact diagnostic format, but even without an output schema this is enough to call the tool correctly.

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 description coverage is 100 percent, so the schema already explains both source and filename. The description adds no parameter-level detail beyond the schema, which is acceptable and warrants the baseline.

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 uses a specific verb and object: verify/check SvGrid code against the current version's exported surface. It details exactly what is validated (SVGrid props, ColumnDef keys, grid API methods, importable symbols, theme files, Svelte 5 runes) and clearly distinguishes this from the sibling lookup/search 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?

The description explicitly states when to use the tool: before handing code to the user, on every file that uses SvGrid, with a fix-and-rerun workflow. It doesn't explicitly describe when not to use it or compare it with siblings, but the context is clear and actionable.

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

All SvGrid 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
Disambiguation4/5

The search→fetch and list_examples→get_example_source pairs form clear workflows, and check_svgrid_code is distinct. The only real ambiguity is that fetch also accepts a demo id, which overlaps somewhat with get_example_source, though fetch returns page text rather than .svelte source.

Naming Consistency4/5

Most tools follow a descriptive verb_noun pattern: get_api_reference, get_example_source, list_examples, check_svgrid_code. The bare verbs search and fetch are minor deviations, but the names remain predictable and easy to distinguish.

Tool Count5/5

Six tools is a tight, well-scoped set for a documentation-and-code-support server. Each tool earns its place and together they cover discover, read, reference, example, and verify workflows without redundancy.

Completeness5/5

The tool surface covers the full assistant loop: search documentation, fetch doc content, read the API reference, browse and copy demo source, and validate code against the real SvGrid API. There is no obvious missing operation that would create a dead end for an agent.

Resources