Skip to main content
Glama

blueprint-modular

by com.blueprint-modular.mcp

Suggérer une composition

suggest_composition
Read-only

Suggère une liste de composants Blueprint Modular répondant à un besoin décrit en langage naturel, en raisonnant sur la couche sémantique (rôle, frame Ω, guidance) : chaque suggestion explicite son sens (meaning) et ses associations sémantiques (pairWith). À UTILISER pour partir d'une intention d'écran (ex. 'un dashboard avec des métriques et un graphique') et obtenir les briques pertinentes. Réponse bornée.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
needYesDescription du besoin / de l'écran à construire.
limitNoNombre max de suggestions (défaut 8 ; plafonné à 12). Optionnel.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true. Description adds value by explaining the reasoning on the semantic layer and that each suggestion includes meaning and pairWith. No contradiction.

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 sentences, front-loaded with purpose, no wasted words. Efficient and clear.

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?

No output schema exists, so description should cover return structure. It mentions meaning and pairWith but lacks details on limit behavior and default. Adequate but incomplete.

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 the schema documents both parameters. Description adds no extra meaning beyond the schema, satisfying 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?

Description clearly states the verb 'suggère' and resource 'liste de composants Blueprint Modular', and distinguishes from sibling tools (get, list, search) by focusing on natural language need and semantic reasoning.

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?

Explicitly says 'À UTILISER pour partir d'une intention d'écran', providing clear context. However, it does not mention when not to use or alternatives.

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

All blueprint-modular 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.4/5.0
Disambiguation5/5

Each tool serves a distinct purpose: getting details of a specific component, listing all components, searching by keyword, and suggesting compositions based on intent. No overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case: get_component, list_components, search_components, suggest_composition.

Tool Count5/5

With 4 tools, the set is well-scoped for a component catalog: list, search, get detail, and suggest composition. Neither too few nor too many.

Completeness5/5

The tool set covers the main use cases for a read-only design system catalog: browsing, searching, retrieving details, and getting composition suggestions. No obvious gaps.

Resources