Skip to main content
Glama
Sign In
engineering-matrix-explorer

engineering-matrix-explorer

by officechbusinessservices-creator
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_repository_boilerplate

Retrieve starter boilerplate files for any tool or framework to jumpstart your project setup.

Instructions

Get starter boilerplate files for a specific tool or framework

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "toolName": "<toolName>"
    },
    "name": "get_repository_boilerplate"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolNameYesTool name e.g. 'TypeScript', 'FastAPI', 'Docker'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

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 reveal behavioral traits. It only says 'Get starter boilerplate files' with no mention of side effects, error handling (e.g., unknown tool), or whether files are generated/static. This is insufficient.

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?

Single sentence with no fluff. Every word is necessary. Front-loaded with verb and resource.

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

Completeness3/5

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

For a simple tool with one parameter, the description is adequate but lacks detail on what the boilerplate files contain or how they are returned (e.g., as a download or inline). No output schema exists to supplement.

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 has 100% coverage with a description for toolName that includes examples. The tool description adds no additional meaning beyond what the schema already provides, so 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?

Description clearly states the action (Get) and resource (starter boilerplate files) and specifies it's for a specific tool or framework. It distinguishes from sibling tools list_categories and search_engineering_matrix.

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not-to-use guidance is provided. Usage is implied: call this when you need starter files for a tool. No alternatives or exclusions mentioned.

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

Deploy Server

Other Tools