Skip to main content
Glama

Set up DIYA

get_setup
Read-onlyIdempotent

The install command and the exact root files for an app (Next.js App Router providers and layout, or Vite's main.tsx), Tailwind v4 layer order, and DIYA's rules. Call it once per app, before writing components.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
chartsNoThe app needs Data Viz charts (adds echarts@6)
tailwindNoThe app uses Tailwind v4
frameworkNonext if left out
packageManagerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real value on top by disclosing what the call actually yields (install command, root file contents, layer order, rules) and the 'once per app' idempotence expectation. It does not describe the response shape or how the framework-dependent output differs, keeping it at a 4 rather than 5.

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?

A single dense sentence that front-loads the highest-value deliverable (install command and root files) and closes with the actionable call directive. The parenthetical adds specificity rather than padding, though the fragment structure makes the opening slightly harder to parse.

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?

With 4 optional parameters, 75% schema coverage, no output schema, and full annotation coverage, the description supplies what's needed: what the tool returns, when to call it, and how often. The remaining gap is how each parameter changes the returned files, which is minor given the schema's own descriptions.

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 75%, so the schema already documents charts, tailwind, and framework; the description adds no meaning to any of them. Its mention of 'Next.js App Router ... or Vite' loosely echoes the framework enum but never ties it to the parameter, and packageManager (the undocumented one) is not addressed at all. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates the concrete artifacts returned: the install command, exact root files (Next.js App Router providers/layout or Vite main.tsx), Tailwind v4 layer order, and DIYA's rules. That is a specific resource bundle distinguishable from siblings like get_component or get_theme, though the opening has no explicit verb (it reads as a fragment rather than 'Returns ...').

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?

'Call it once per app, before writing components' gives explicit timing and cardinality guidance, which is the key decision an agent must make with this tool. It stops short of stating when NOT to call it or naming an alternative, but the ordering constraint is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources