run_salary_comparison
Compare salary taxation and net outcomes for a country.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| country | Yes | ||
| currency | Yes | ||
| gross_salary | Yes |
popadex-personal-finance
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.4/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description must fully disclose behavior. It only states a comparison function but does not mention if it is read-only, requires authentication, has rate limits, or produces side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single short sentence, which is concise but under-specified. It could include more detail without being verbose, so it does not fully earn 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 lack of output schema, annotations, and presence of related sibling tools, the description is incomplete. It does not explain return values, how to interpret results, or what constitutes 'net outcomes'.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description adds minimal value. 'Compare salary taxation and net outcomes for a country' does not explain the meaning or format of the parameters (country, currency, gross_salary) beyond what the schema already shows.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose3/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states the tool compares salary taxation and net outcomes, which gives a general purpose but lacks specificity. It does not distinguish clearly from sibling tools like run_tax_estimate or compare_disposable_income, and 'net outcomes' is vague.
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?
No guidance on when to use this tool over alternatives such as run_tax_estimate or compare_disposable_income. The description does not mention prerequisites or context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3.2/5.0
Disambiguation5/5
Each tool targets a distinct aspect of personal finance (budget, country comparisons, portfolio, net worth, retirement, salary, tax) with no apparent overlap in functionality.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern in snake_case, using verbs like 'build', 'compare', 'export', 'get', 'run' followed by a descriptive noun phrase.
Tool Count5/5
With 11 tools covering various personal finance analysis tasks, the count is well-scoped—neither too few to be useful nor too many to cause confusion.
Completeness4/5
The set covers key areas like budget, portfolio, net worth, retirement, salary, and tax, but may lack more granular operations like transaction management, which could be intentional for an analysis-focused server.