Source-backed Sri Lanka payslip tools for APIT/PAYE, EPF, ETF, stamp duty, and net pay.
Estimate monthly APIT/PAYE, employee and employer EPF, ETF, stamp duty, net pay, and employer cost for regular primary employment in Sri Lanka.
| Name | Required | Description | Default |
|---|---|---|---|
| grossSalary | Yes | Gross monthly employment income in Sri Lankan rupees | |
| epfEtfEarningsBase | No | EPF/ETF-eligible monthly earnings; defaults to gross salary | |
| otherEmployeeDeductions | No | Optional non-statutory employee deductions, such as a loan repayment |
| Name | Required | Description |
|---|---|---|
| apit | Yes | |
| netPay | Yes | |
| caution | Yes | |
| sources | Yes | |
| currency | Yes | |
| stampDuty | Yes | |
| employeeEpf | Yes | |
| employerEpf | Yes | |
| employerEtf | Yes | |
| grossSalary | Yes | |
| employerCost | Yes | |
| methodologyUrl | Yes | |
| sourceTableYear | Yes | |
| yearOfAssessment | Yes | |
| epfEtfEarningsBase | Yes | |
| payslipGeneratorUrl | Yes | |
| otherEmployeeDeductions | Yes | |
| totalEmployeeDeductions | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate read-only, idempotent, non-destructive behavior. The description adds context by listing the specific calculated outputs (APIT/PAYE, EPF, ETF, etc.) and confirming the estimation nature, consistent with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-formed sentence of 25 words that front-loads the tool's purpose and lists key outputs without any extraneous content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the scope (regular primary employment in Sri Lanka) and lists all major components. Given the existence of an output schema and comprehensive annotations, it is complete enough for a calculation tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with descriptive parameter comments. The description provides a high-level context but does not add any new meaning beyond what the schema already states for each parameter. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description specifies the verb 'Estimate' and the resource: monthly APIT/PAYE, EPF, ETF, stamp duty, net pay, and employer cost. It clearly distinguishes from sibling tools (reference and checklist) by focusing on computation of payslip components.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description does not provide any guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use it, or compare with sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Return the maintained APIT, EPF, ETF, and stamp-duty assumptions with official Sri Lankan sources and scope limits.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
| scope | Yes | |
| period | Yes | |
| sources | Yes | |
| citation | Yes | |
| currency | Yes | |
| openApiUrl | Yes | |
| effectiveFrom | Yes | |
| excludedCases | Yes | |
| methodologyUrl | Yes | |
| provenanceNote | Yes | |
| employeeEpfRate | Yes | |
| employerEpfRate | Yes | |
| employerEtfRate | Yes | |
| sourceTableYear | Yes | |
| yearOfAssessment | Yes | |
| monthlyApitRelief | Yes | |
| stampDutyThreshold | Yes | |
| stampDutyAboveThreshold | Yes | |
| machineReadableMethodologyUrl | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate the tool is read-only, idempotent, and non-destructive. The description adds value by disclosing the specific data returned (APIT, EPF, ETF, stamp-duty) and the inclusion of official sources and scope limits, which confirm safe querying behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-formed sentence that conveys the essential information without any wasted words. It is concise and front-loaded with the primary action.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple, parameterless tool with an output schema, the description is complete. It clarifies the content and provenance of the data, which is sufficient for the agent to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With zero parameters and 100% schema coverage, the description need not explain param semantics, but it still adds meaning by enumerating what the tool returns, which enhances the agent's understanding of the output without parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description specifies exactly what the tool returns (APIT, EPF, ETF, stamp-duty assumptions) and distinguishes it from sibling tools like calculate_sri_lanka_payslip and get_sri_lanka_payslip_checklist by focusing on reference data rather than calculations or checklists.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool should be used when reference assumptions are needed but does not explicitly state when to use it versus alternatives or when not to use it. The sibling names provide some context, but the description itself lacks explicit usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Return the fields and checks needed to prepare or review a Sri Lankan employee payslip.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
| sources | Yes | |
| earnings | Yes | |
| guideUrl | Yes | |
| evidenceNote | Yes | |
| generatorUrl | Yes | |
| identityAndPeriod | Yes | |
| employeeDeductions | Yes | |
| verificationChecks | Yes | |
| employerContributions | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so safety is clear. Description adds context that the tool returns fields and checks, which is consistent and adds value beyond bare annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence of 14 words, front-loaded with the main action and resource. No extraneous content; every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no parameters, output schema available, and annotations covering behavior, the description is sufficient. It explains the tool's purpose clearly, and no further information is needed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist, so baseline is 4. Description does not need to add parameter info; schema coverage is 100% trivially. No missing semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it returns fields and checks for a Sri Lankan payslip, using a specific verb ('return') and resource. It distinguishes from siblings: 'calculate_sri_lanka_payslip' for computation, 'get_sri_lanka_payroll_reference' for reference data.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Description implies use when preparing or reviewing a payslip, but does not explicitly state when not to use or mention alternative sibling tools. Guidance is adequate but not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user or an account that owns the GitHub organization, then choose Claim with GitHub.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Nigeria PAYE, VAT and CBN rates, sourced and dated. Plus invoice totals, QR codes, JSON, Base64.
Live US paycheck and payroll-tax math for 2026, all 50 states and DC, powered by tools-berry.com.
Verified 2026 Canadian payroll math: employer total cost, employee take-home, net-to-gross. Free.
90+ pure finance calculators: loans, investing, bonds, options, tax. Stateless, stores nothing.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: calculation, reference data, and checklist. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (calculate_..., get_...), with clear and descriptive naming.
With 3 tools, the server is well-scoped for its narrow domain of Sri Lanka payslip processing. Each tool is essential.
The set covers calculation, reference assumptions, and a checklist, which are sufficient for basic payslip tasks. Minor gaps like handling edge cases or multiple employments are absent but within the stated scope.
