Skip to main content
Glama
Sign In
Mushi-Mushi

Mushi-Mushi

by kensaurus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Design score actions

get_design_settings
Read-onlyIdempotent

Fetch a project's design deviance configuration—threshold, CI failure, autofix, auto-fix toggle, and edit rights—to verify what the score enforces.

Instructions

Return what the design deviance score may do on its own for one project: threshold (0–100; the actions fire above it), failCi (mushi recipe check --push fails CI above it), autofix (new warn/error findings above it dispatch a fix) and autofixEnabled (the project auto-fix switch, without which the design auto-fix does nothing), plus canEdit. Optional projectId. Read-only.

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_design_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdNoProject UUID — defaults to the server-configured project when omitted (`project_id` is accepted too.)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.14

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered; the description adds real domain semantics beyond that, explaining what each flag actually does (threshold fires actions above it, failCi fails CI on push, autofix dispatches fixes, autofixEnabled gates the whole auto-fix behavior). It doesn't describe error or fallback behavior when no project is configured, so it stops short of a 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 plus two short trailing fragments; the returned fields are front-loaded and the read-only nature is stated last. It is efficient with no filler, though cramming four field definitions into one sentence slightly hurts scannability.

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 no output schema, the description carries the burden of describing the return value, and it does so by naming all five fields and their meanings. An agent knows what it gets back and that omission of projectId is safe; only the fallback/error case is unaddressed.

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%, so the single projectId parameter is already fully documented including the snake_case alias. The description only restates that projectId is optional, adding no syntax or scoping detail beyond the schema; baseline 3 applies.

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 clearly states the verb and resource: it returns the design deviance score's actionable settings for one project, and enumerates the specific fields returned (threshold, failCi, autofix, autofixEnabled, canEdit). It does not explicitly name the write counterpart set_design_settings, but 'Read-only' implicitly frames it against that sibling.

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?

Usage is only implied: an agent can infer this is the read-side of the settings pair and that projectId scopes it to one project or falls back to the server-configured one. There is no explicit 'use this when... / use set_design_settings when...' routing, which would matter given the paired write tool in the sibling list.

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