Tempo de contribuição (CNIS): soma os vínculos contando concomitância uma vez e converte atividade especial em comum (fatores EC 103/2019, só até 13/11/2019). Retorna tempo total e se atinge o tempo antigo (35H/30M).
| Name | Required | Description | Default |
|---|---|---|---|
| sexo | Yes | ||
| vinculos | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly and idempotent, and the description adds valuable behavioral rules: concurrent bonds are counted once, special activity is converted to common using EC 103/2019 factors only up to 13/11/2019, and it returns both total time and attainment of the old-age threshold. This goes well beyond the 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?
Two dense sentences carry the full purpose, key algorithm rules, legal cutoff, and output summary. There is no filler, and the most identifying information is front-loaded.
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 no-output-schema, read-only calculation tool with moderately complex rules, the description covers the core inputs, the main calculation nuance (concomitance and special conversion cutoff), and the return value. It could be more explicit about input date formats or exact conversion factors, but nothing essential to choosing or invoking it is missing.
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 description coverage is 0%, so the description must compensate. It does clarify the meaning of 'vinculos' (employment bonds to sum), the role of 'sexo' via the 35H/30M thresholds, and the notion of special activity conversion tied to the tipo values. It does not spell out date formats or enumerate each enum value, but it gives the essential 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 names the resource ('Tempo de contribuição (CNIS)') and states a specific computation: summing employment bonds, counting concurrent periods once, and converting special activity into ordinary time. It also states the output (total time and whether the old-time threshold 35H/30M is reached), which fully distinguishes it from sibling tools like calculo_rmi or calculo_pensao.
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 context of use is implied: it is for calculating contribution time from CNIS records, not for calculating benefits or other legal indices. However, it does not explicitly name alternatives or state when not to use this tool versus the many sibling 'calculo_*' tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The 16 calculation tools are each tied to a distinct legal scenario (rent, criminal sentencing, FGTS, labor severance, etc.), so misselection is unlikely. However, the platform meta-tools overlap: connect, toolkit_info, and authenticate all deal with connection/auth state, and marketplace's list_tools/describe overlaps with toolkit_info.
The legal calculators use a consistent calculo_<domain> prefix, which is highly predictable. But the six meta-tools use standalone English names (connect, marketplace, report_bug) and the prefix itself mixes nouns (calculo_aluguel) with a verb (calculo_atualizar), so the overall convention is not uniform.
22 tools is on the heavy side for a server claiming to be about 'juros e multa', especially since six tools are unrelated platform administration features. The 16 legal calculators are arguably well-scoped, but the meta-tool wrapper inflates the count and blurs the server's purpose.
The legal calculation surface is unusually broad: civil, criminal, labor, social security, banking, and family law are all represented, and the calculo_atualizar tool provides the generic debt-update/interest/fee calculation implied by the server name. Minor gaps exist—there is no dedicated simple-interest-only calculator or court-fees/custas calculator—but no obvious dead-end workflows remain.