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 mark the tool as read-only, idempotent, and non-destructive. The description adds meaningful behavioral details: overlapping bonds are counted once, special activity is converted to ordinary time, conversion applies only until 13/11/2019, and the result includes a threshold indicator.
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 front-load the computation purpose, then the output. Every phrase adds information—concurrency handling, date cutoff, special-activity conversion, thresholds, and return value—with no filler.
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 complex calculation tool with no output schema and no parameter descriptions, the description gives the core algorithm, cutoff date, and return semantics. Yet it omits operational details such as date format, how the tipo enum maps to conversion factors, and special handling for PROFESSOR, which an agent would need for robust invocation.
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 carry parameter meaning. It clarifies vinculos as employment bonds whose periods are summed, sexo by referencing the 35H/30M thresholds, and special-activity values in the tipo enum. However, it does not explain the date format for inicio/fim or the meaning of the PROFESSOR enum value.
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 states a specific computation: summing vínculos while counting concurrent periods once, converting special activity to common time, and returning total time plus a threshold check. This clearly identifies it as a contribution-time calculator and distinguishes it from unrelated calculo_* siblings, though it does not explicitly name an alternative.
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 establishes the tool's domain (CNIS contribution time) and the key conditions, such as special-activity conversion only through 13/11/2019 and the 35H/30M old-time threshold. It does not explicitly state when not to use the tool or point to a sibling alternative, but the usage context is clear.
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 calculo_* tools each target a distinct legal area (labor, FGTS, alimony, sentencing, INSS, etc.), and detailed descriptions clarify their boundaries. Some relationship exists among correction/index-based calculators, but the legal context makes them distinguishable. The platform tools are also separate from the domain calculators, though marketplace is broad.
All 16 calculation tools follow a consistent `calculo_<area>` snake_case pattern, which is good. However, the six platform/admin tools use a different style and language (authenticate, connect, marketplace, report_bug, show_version, toolkit_info), creating a clear split between the two clusters.
At 22 tools, the set is on the heavy end. The 16 legal calculators each earn their place for a broad Brazilian legal-calculation suite, but the additional platform and marketplace plumbing tools inflate the count and make the server feel less focused.
The tool surface covers a wide range of Brazilian legal calculation needs: labor, FGTS, criminal sentencing, prison progression, INSS benefits, alimony, divorce, banking revisions, and monetary correction. Minor gaps exist, such as dedicated overtime or additional-hours calculators, but the core workflows are well covered with no obvious dead ends.