create_energy_assessment
Start a new assessment session. Free. [free]
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
energyai
TDQS
B3.3/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It only states the action and free cost, but does not explain what starting a session entails, such as session identifiers, persistence, or next steps. Minimal behavioral disclosure.
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 very short and front-loaded with the core action. However, 'Free. [free]' is redundant repetition, slightly detracting from 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 numerous sibling tools, the description does not situate the assessment session within the broader workflow. It lacks information on what happens after starting, making it less complete for an agent deciding whether to invoke this tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters (schema coverage 100%), so there is no parameter semantics for the description to clarify. Baseline 4 is appropriate for a zero-parameter tool.
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 uses the specific verb 'Start' and the resource 'assessment session', clearly indicating the tool initiates a new session. It distinguishes from siblings like 'complete_energy_assessment' through the start/complete contrast.
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?
There is no guidance on when to use this tool versus alternatives like 'answer_energy_assessment_question' or 'complete_energy_assessment'. The description fails to provide context on the assessment flow or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
C2.8/5.0
Disambiguation2/5
Several tools overlap heavily: get_node_score vs get_energy_node_score, find_local_installers vs match_installers, and route_lead vs submit_contractor_match_request are easy to confuse. The descriptions clarify details, but an agent would often need to inspect arguments to know which installer, incentive, or recommendation tool is the right one.
Naming Consistency3/5
All tool names use snake_case with a verb-leading style, which provides a consistent backbone. However, domain naming is inconsistent: the same concept appears as node vs energy_node, installer vs contractor, and incentive discovery is split across check_incentives, get_energy_incentives, list_guides, and get_guide without a predictable pattern.
Tool Count2/5
29 tools is too many for a single MCP server, especially since several fall into overlapping installer/lead, incentive, recommendation, and commercial-power categories. Many tools appear to be monetization gates or handoff variants that could reasonably be consolidated.
Completeness3/5
The set covers core user journeys: assessment creation/answering/completion, incentive guidance, installer discovery and routing, quote review, and commercial power screens. However, there are notable gaps in state management, such as no way to list or retrieve existing assessments/leads, and several checkout or handoff tools have no follow-up/status tool.