Skip to main content
Glama

smart_score

Manage project health scores by recalculating, syncing, diagnosing, optimizing, and resetting scores across tools.

Instructions

Central coordination for project health scoring system - recalculate, sync, diagnose, optimize, and reset scores across all MCP tools

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
intentIdNoIntent ID to get score trends for (for get_intent_scores operation)
todoPathNoPath to TODO.md file (for sync_scores operation)TODO.md
componentNoScore component to reset (for reset_scores operation)all
operationYesSmart scoring operation to perform
componentsNoScore components to recalculate (for recalculate_scores operation)
forceUpdateNoForce update even if data is fresh
previewOnlyNoPreview changes without applying (for optimize_weights operation)
projectPathYesPath to project directory
analysisModeNoMethod for weight optimization (for optimize_weights operation)current_state
triggerToolsNoTools to trigger for fresh data (for sync_scores operation)
customWeightsNoCustom weight overrides (for optimize_weights operation)
updateSourcesNoTrigger source tool updates before recalculating
includeHistoryNoInclude score history analysis (for diagnose_scores operation)
preserveHistoryNoPreserve score history in backup (for reset_scores operation)
rebalanceWeightsNoRecalculate optimal scoring weights (for sync_scores operation)
checkDataFreshnessNoValidate data freshness across tools (for diagnose_scores operation)
suggestImprovementsNoProvide score improvement suggestions (for diagnose_scores operation)
recalculateAfterResetNoImmediately recalculate after reset (for reset_scores operation)
Behavior2/5

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

With no annotations, the description carries full burden but fails to disclose side effects, destructive actions, or auth requirements. It merely lists operations without behavioral details.

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 sentence that front-loads the purpose, but it is somewhat long. Slightly below excellent conciseness.

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

Completeness2/5

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

Given the tool's complexity (18 params, 7 operations, no output schema), the description is insufficient. It does not explain when to use each operation or what the output includes.

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 baseline 3. The description adds no extra meaning beyond the schema; it only provides a high-level overview.

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 tool's role as central coordination for project health scoring and lists multiple operations, distinguishing it from sibling analysis tools. However, it lacks a specific action verb for the overall purpose.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus the many sibling tools. The description only lists operations without context on typical scenarios or prerequisites.

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/tosin2013/mcp-adr-analysis-server'

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