Skip to main content
Glama
amarodeabreu

Sensei MCP

by amarodeabreu
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_engineering_guidance

Get engineering guidance through multi-persona orchestration that analyzes your query from diverse perspectives and returns synthesized recommendations.

Instructions

Get engineering guidance via multi-persona orchestration (DEFAULT in v0.3.0).

⚠️ DEPRECATION NOTICE (v0.6.0): This tool will be deprecated in v0.7.0. Please use the new granular tools instead:

  • suggest_personas_for_query() - Get persona suggestions

  • get_persona_content() - Get persona SKILL.md content

  • get_session_context() - Get session memory

  • record_consultation() - Record consultation after analysis

The new architecture provides content for Claude to analyze, rather than trying to perform analysis within the MCP server.

This is the NEW primary tool for getting engineering guidance. The Skill Orchestrator coordinates 21 specialized personas to provide holistic, multi-perspective analysis of your engineering questions.

Args: query: Your question or scenario mode: Analysis mode: - "orchestrated" (DEFAULT): Multi-persona analysis with intelligent selection - "quick": Single persona (Snarky Senior Engineer) for fast answers - "crisis": Emergency team (Incident Commander, SRE, Executive) - "standards": Legacy mode (engineering standards only, no personas) session_id: Session identifier project_root: Absolute path to project root (for local rules/sessions) specific_personas: Override auto-selection (e.g., ["security-sentinel", "pragmatic-architect"]) output_format: Response format ("brief", "standard", "executive")

Returns: Orchestrated multi-perspective guidance with synthesis and recommendations

Examples: # Auto-orchestrated (DEFAULT) get_engineering_guidance( query="Should we migrate to microservices?", session_id="saas-backend" )

# Crisis mode
get_engineering_guidance(
    query="Production database is down",
    mode="crisis"
)

# Specific personas
get_engineering_guidance(
    query="Review this payment API design",
    specific_personas=["security-sentinel", "api-platform-engineer"]
)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoorchestrated
queryYes
session_idNodefault
project_rootNo
output_formatNostandard
specific_personasNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

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 does disclose orchestration behavior, default mode, return value shape, and legacy standards mode. It also explains the architectural intent (content for Claude to analyze rather than in-server analysis), though it omits permission or rate-limit context.

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?

The description is well-structured with Args, Returns, and Examples sections, making it easy to scan. However, the deprecation notice and contradictory status lines add considerable confusing baggage that could be trimmed without losing essential information.

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?

For a complex orchestration tool with multiple modes and alternatives, the description covers purpose, parameters, return semantics, and provides examples. The contradiction between deprecation and 'primary tool' status is a notable gap that affects completeness, but the presence of an output schema reduces the burden for return-value documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage for its six parameters, but the description fully compensates by explaining every parameter, including mode enum values, persona overrides, session/project context, and output format. This adds significant meaning beyond the raw schema.

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 opening line clearly specifies the tool's function (get engineering guidance) and mechanism (multi-persona orchestration), distinguishing it from the granular sibling tools. However, the deprecation notice telling users to prefer new granular tools conflicts with the later claim that this is the NEW primary tool, which slightly muddies the intended purpose.

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 names alternative granular tools and says to use them instead, while also documenting mode-specific use cases (quick, crisis, standards, specific personas). The contradictory statement calling this the 'NEW primary tool' weakens the guidance, preventing a perfect score.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/amarodeabreu/sensei-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server