Skip to main content
Glama
rajmohancoder

Insurance Premium Calculator

by rajmohancoder
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

Server Quality Checklist

58%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v1.0.0

  • Disambiguation5/5

    Each tool has a clearly distinct purpose: calculate_basic_premium handles standard insurance, calculate_health_premium focuses on health-specific factors, and compare_policies provides comparison across types. There is no overlap or ambiguity between these functions.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case (calculate_basic_premium, calculate_health_premium, compare_policies). The naming is predictable and readable throughout the set.

    Tool Count3/5

    With only 3 tools, the set feels thin for an insurance premium calculator domain. While the tools cover core calculations and comparison, additional operations like updating policies or handling claims might be expected, making the count borderline for the scope.

    Completeness3/5

    The tools cover basic premium calculations and comparison, but there are notable gaps for a full insurance domain, such as missing CRUD operations for policies, handling claims, or managing customer data. Agents can work around this for simple tasks but may fail in more complex scenarios.

  • Average 3/5 across 3 of 3 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • No community issues in the last 6 months
    • 0 commits in the last 12 weeks
    • No stable releases found
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI status not available

  • Add a LICENSE file by following GitHub's guide. Once GitHub recognizes the license, the system will automatically detect it within a few hours.

    If the license does not appear after some time, you can manually trigger a new scan using the MCP server admin interface.

    MCP servers without a LICENSE cannot be installed.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • Add a glama.json file to provide metadata about your server.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • 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 of behavioral disclosure. It states the tool calculates a premium but doesn't describe how the calculation works, whether it's deterministic or approximate, if there are rate limits, or what the output format is. For a calculation tool with zero annotation coverage, this lacks critical behavioral context.

    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 a single, efficient sentence that front-loads the core purpose. It wastes no words but could be slightly more structured by including usage context. It's appropriately sized for a simple tool, though it lacks depth that might be needed given the absence of annotations.

    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 tool's complexity (a calculation with 3 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain the calculation method, output format, or error conditions. The agent is left guessing about behavioral aspects, making this inadequate for reliable tool invocation.

    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 all parameters with descriptions and constraints. The description adds no additional meaning beyond what the schema provides, such as explaining interactions between parameters or calculation logic. Baseline 3 is appropriate when the schema does the heavy lifting.

    Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

    Purpose4/5

    Does the description clearly state what the tool does and how it differs from similar tools?

    The description clearly states the verb 'calculates' and the resource 'basic insurance premium', making the purpose evident. It distinguishes from sibling tools like 'calculate_health_premium' by specifying it handles multiple policy types, though it doesn't explicitly contrast with 'compare_policies'. The description is specific but could be more precise about its scope relative to siblings.

    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?

    The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'calculate_health_premium' or 'compare_policies', nor does it specify prerequisites, exclusions, or appropriate contexts. Usage is implied by the parameters but not explicitly stated, leaving the agent to infer when this tool is suitable.

    Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

  • Behavior2/5

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

    With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool calculates premiums including pre-existing conditions, but doesn't describe what the calculation returns (e.g., a numeric value, structured data), error conditions, rate limits, or authentication needs. For a calculation tool with zero annotation coverage, this leaves significant gaps.

    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, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with every word earning its place.

    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 complexity of a premium calculation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the tool returns (e.g., a premium amount, breakdown details), how pre-existing conditions affect the calculation, or any behavioral aspects. This leaves the agent guessing about the tool's output and usage.

    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 all four parameters thoroughly. The description mentions 'including pre-existing conditions', which aligns with one parameter but doesn't add meaningful semantic context beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

    Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

    Purpose4/5

    Does the description clearly state what the tool does and how it differs from similar tools?

    The description clearly states the verb 'calculates' and the resource 'health insurance premium', specifying it includes pre-existing conditions. However, it doesn't explicitly differentiate from sibling tools like 'calculate_basic_premium' or 'compare_policies', which likely have related but distinct purposes.

    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?

    The description provides no guidance on when to use this tool versus alternatives like 'calculate_basic_premium' or 'compare_policies'. It doesn't mention prerequisites, exclusions, or contextual factors that would help an agent choose appropriately among siblings.

    Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

  • Behavior2/5

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

    No annotations are provided, so the description carries full burden. It states the tool 'compares premium' but doesn't disclose behavioral traits like whether it's read-only, what the output format is (e.g., list, table), or any constraints (e.g., rate limits, authentication needs). This is a significant gap for a tool with no annotation coverage.

    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, efficient sentence with zero waste—front-loaded and appropriately sized for the tool's purpose. Every word earns its place.

    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 no annotations, no output schema, and a tool that performs comparison (implying potential complexity), the description is incomplete. It lacks details on output format, behavioral constraints, and how it differs from siblings, making it inadequate for full agent understanding.

    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 both parameters (age, coverage_amount). The description adds no additional meaning beyond implying these are used for comparison, matching the baseline when schema does the heavy lifting.

    Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

    Purpose4/5

    Does the description clearly state what the tool does and how it differs from similar tools?

    The description clearly states the action ('compares premium') and scope ('for all policy types'), with specific inputs ('given age and coverage'). It distinguishes from sibling tools by covering multiple policy types rather than specific ones like 'basic' or 'health', though it doesn't explicitly name the siblings.

    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 usage when needing premium comparisons across policy types, but doesn't explicitly state when to use this versus the sibling tools (calculate_basic_premium, calculate_health_premium) or any exclusions. Context is clear but lacks alternative guidance.

    Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

simple-mcp-test MCP server

Copy to your README.md:

Score Badge

simple-mcp-test MCP server

Copy to your README.md:

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/rajmohancoder/simple-mcp-test'

If you have feedback or need assistance with the MCP directory API, please join our Discord server