Scored across 8 tools
Tools are generally distinct with clear domains: policy (permissions), guardrail (content safety), spend (analytics), budget (limits), compliance (audit), alerts (incidents), and provider health. Minor semantic overlap exists between check_spend and get_budget_status (both financial), and between check_policy and evaluate_guardrail (both validation), but descriptions clarify their distinct scopes.
Consistent snake_case prefixing (thinkneo_) and mostly verb_noun structure (check, evaluate, get, list, schedule). Minor deviation with provider_status which lacks a verb prefix, breaking the pattern established by get_budget_status and get_compliance_status. Verbs vary (check/evaluate/get) but remain readable.
Eight tools is a reasonable count for an AI governance control plane, covering policy, cost, compliance, and operational monitoring. The inclusion of schedule_demo (a sales/marketing function) is slightly incongruous with the operational focus of the other seven tools, but doesn't bloat the set.
Strong observability coverage (read-only status checks, spend analysis, alert listing) but lacks expected control plane capabilities: no tools to create/update policies, set budgets, configure guardrails, or manage/acknowledge alerts. The surface is adequate for monitoring but incomplete for 'control' operations implied by the server name.