MCP server for Sherpa financial modeling and scenario analysis platform
17 tools with mixed quality. Naming is verb-forward and clear (get_, upsert_, delete_, etc.), following pattern:tool conventions. Descriptions present but brief (avg ~80 chars, below 194-char baseline). Input schemas visible with proper types and enums for constrained fields (entity_type, format, action). Critical gaps: output schemas undocumented across all tools; no error handling guidance; no pagination support despite tools like export_scenario and import_snapshot that could return large results; parameter descriptions sparse (many lack context on valid ranges, formats, or dependencies). Security concern: initialize_setup accepts companyName/currency as params but no auth/permission checks visible. Composition issue: upsert_entity_override accepts a generic 'override' object with 15+ optional fields, LLM must guess which fields apply to which entity_type.
Add a dependency relationship between two services
Delete per-scenario entity override for a specific entity
Delete monetization configuration for an entity
Delete a pack
Delete a service dependency relationship
Export scenario data in JSON or CSV format
Retrieve per-scenario entity override for a specific entity (service, cost, provider, or plan)
Get monetization configuration for an entity (service, pack, or plan)
Output schemas completely undocumented. No tool declares what fields it returns, forcing LLMs to infer structure from trial-and-error. Violates pattern:tool and pattern:response-shaper.
upsert_entity_override and upsert_monetization_config accept generic 'override'/'config' objects with 15+ optional fields. No documentation of which fields apply to which entity_type. LLM cannot determine valid input without trial-and-error.
No error handling guidance. Tools do not document what errors are retryable, user-fixable, or fatal. No recovery hints (e.g., 'scenario not found, try list_scenarios first'). Violates pattern:recovery-guide.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 49 | 2026-07-28+ | v2 |
Liveness/identity probe for the MCP launcher
Import a complete scenario snapshot with providers, services, packs, plans, costs, verticals, cohorts, and overrides
Import customer/user base data from CSV with preview and import actions
Initialize application setup with company settings and optionally clear sample data
Refresh exchange rates from Frankfurter API and update settings
Resolve effective monetization configuration per service after inheritance and scenario overrides are applied
Sync predefined provider rows with bundled price list
Create or update per-scenario entity override for a specific entity
Create or update monetization configuration for an entity
initialize_setup lacks permission checks and audit trail. Accepts companyName/currency/discountRate without verifying caller authority. Destructive operation (clears sample data) with no confirmation step. Violates pattern:permission-gate and pattern:confirmation-request.
Descriptions too brief (avg ~80 chars vs 194-char baseline). Many lack context on when to use the tool, what it returns, or dependencies. E.g., 'Refresh exchange rates from Frankfurter API' does not explain what happens to existing rates or when to call this.