Skip to main content
Glama
Sign In

Untax

by io.untax
OverviewDiscussionsAdmin

parse_scra_dmdc_certificate

Read-onlyIdempotent

Parse DoD Defense Manpower Data Center (DMDC) Active Duty Status Report text to verify active military service and calculate SCRA 6% tax interest cap protections.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "certificate_text": "<certificate_text>"
    },
    "name": "parse_scra_dmdc_certificate"
  }
}

Input Schema

NameRequiredDescriptionDefault
certificate_textYesPasted text from official DoD DMDC SCRA Active Duty certificate

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that the tool both extracts active-duty status and performs an interest-cap calculation, but says nothing about handling unparseable or negative-match text, confidence, or what the returned fields are.

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?

One front-loaded sentence with the document type and the two purposes, no filler. Slightly dense with acronym stacking (DoD DMDC SCRA), but every clause carries meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description carries the burden of hinting at return values; it gestures at verification and cap calculation but does not describe the shape of results or failure behavior. For a parse-plus-compute tool this is adequate but leaves the agent guessing about output.

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?

Single parameter with 100% schema description coverage, so the schema already explains that it is pasted certificate text. The description restates the same idea (official DoD DMDC SCRA certificate) without adding format, length, or content expectations beyond the schema. Baseline 3 applies when the schema does the work.

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?

States a specific verb and resource (parse DoD DMDC Active Duty Status Report text) plus the downstream outcome (verify active service, calculate SCRA 6% interest cap). An agent can tell it is a document parser for a specific certificate type, though it never names its closest sibling (parse_va_benefit_letter) or the follow-on audit_scra_interest_cap tool.

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?

Usage is implied by the input constraint: you have pasted DMDC certificate text and need active-duty verification plus the SCRA cap. There is no explicit when-not guidance, no statement about what to do for other document types, and no routing to audit_scra_interest_cap or the VA-letter parser.

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

All Untax toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources