Skip to main content
Glama

smart_score

Recalculate, sync, diagnose, optimize, and reset project health scores across MCP tools for centralized coordination of scoring operations.

Instructions

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

Input Schema

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

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

No annotations are provided, so the description bears full responsibility. It mentions operations like 'reset' and 'recalculate' but does not describe side effects, data persistence, or whether the tool modifies state. The description is too brief to convey behavioral traits beyond the operation names.

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?

The description is a single sentence that packs significant meaning. Every word is necessary; no redundancy or fluff.

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?

Despite the tool having 18 parameters and no output schema, the description provides no context on return values, expected behavior, or integration with other tools. It is insufficient for an agent to fully understand how to use the tool effectively.

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 schema already documents each parameter. The tool description adds little beyond enumerating the operation values. Baseline of 3 is appropriate as the description does not enhance understanding of the parameters beyond what is in the schema.

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?

The description clearly states it is the central coordination for project health scoring, listing specific operations (recalculate, sync, diagnose, optimize, reset). This differentiates it from sibling tools which are individual analysis or action tools.

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?

The description implies it is the main entry point for scoring activities but does not provide explicit guidance on when to use this tool versus alternatives. No when-not-to-use or prerequisites are mentioned.

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