Skip to main content
Glama
Sign In
windai-mcp

windai-mcp

by umedpaliwal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_windai_pricing

Retrieve WindAI pricing for wind resource assessments. View available credit packages, assessment inclusions, and getting started details.

Instructions

Get WindAI pricing information for wind resource assessments. Shows available credit packages, what's included in each assessment, and how to get started.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries full burden and successfully discloses return content structure: available credit packages, assessment inclusions, and onboarding steps. Uses 'Get' and 'Shows' implying safe read-only behavior, though it omits rate limits or caching details.

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?

Two sentences with zero waste. First sentence establishes purpose and scope; second sentence details specific return contents (credit packages, inclusions, getting started). Front-loaded and efficient.

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?

Appropriately complete for a zero-parameter lookup tool. Despite no output schema, the description enumerates the three key data categories returned (packages, inclusions, onboarding). Minor gap: does not indicate if authentication is required or if pricing is static/dynamic.

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?

Zero parameters required. Per guidelines, 0 params = baseline 4. The description appropriately focuses on return value semantics rather than inventing parameter documentation.

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?

Specific verb 'Get' paired with clear resource 'WindAI pricing information for wind resource assessments.' Effectively distinguishes from siblings: compare_wind_sites (comparison), get_wind_estimate (data), get_wind_farm_assessment (execution), and get_windai_model_info (technical specs).

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?

Implies usage context (checking pricing/credits before purchasing assessments) by mentioning 'credit packages' and 'how to get started,' but lacks explicit guidance on when to call this versus operational tools like get_wind_farm_assessment or whether it should be called before spending credits.

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