Skip to main content
Glama

FreeDailyPro Tools

by com.freedailypro.api
OverviewDiscussionsAdmin

converters_state_tax

Read-onlyIdempotent

US state income tax with a 50-state schedule lookup

Input Schema

NameRequiredDescriptionDefault
stateNoUS state (two-letter code such as NY, or the full name; DC included). Looks up that state's 2026 brackets, standard deduction and exemptions. Send this or ratePct.
incomeYesAnnual income subject to state tax, in US dollars.
ratePctNoFlat rate in percent (first-version behaviour). Takes priority over state.
filingStatusNoFiling status for the state schedule. Default single.
includeLocalNotrue adds an average local income tax where the state has local taxes (an estimate). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / filingStatus
      Added value: +{
+  "description": "Filing status for the state schedule. Default single.",
+  "enum": [
+    "single",
+    "married-joint",
+    "married-separate",
+    "head-of-household"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / includeLocal
      Added value: +{
+  "description": "true adds an average local income tax where the state has local taxes (an estimate). Default false.",
+  "type": "boolean"
+}
    • addedInput schema / properties / income / description
      Added value: +"Annual income subject to state tax, in US dollars."
    • addedInput schema / properties / ratePct / description
      Added value: +"Flat rate in percent (first-version behaviour). Takes priority over state."
    • addedInput schema / properties / state
      Added value: +{
+  "description": "US state (two-letter code such as NY, or the full name; DC included). Looks up that state's 2026 brackets, standard deduction and exemptions. Send this or ratePct.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "income",
-  "ratePct"
-]New value: +[
+  "income"
+]
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is clear. The description adds the useful behavioral detail that this uses a 50-state schedule lookup, but it does not explain output behavior, estimation caveats, or the ratePct fallback path.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no wasted text. It immediately states the domain and scope before any caveats, which is appropriate for this definition.

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?

The core invocation path is clear and the schema fully documents parameters, but with no output schema the description does not say what the tool returns, such as an estimated tax amount or breakdown. It also omits that includeLocal is an estimate and that ratePct takes priority over state, though the schema covers those details.

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?

Schema description coverage is 100%, so all five parameters are already documented in detail, including state lookup, income, ratePct priority, filingStatus enum, and includeLocal estimate behavior. The description adds no parameter-specific meaning beyond reinforcing the 50-state schedule context.

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?

The description identifies a specific resource and calculation domain: US state income tax with a 50-state schedule lookup. It is clear enough to distinguish this from most non-tax siblings, though it does not explicitly contrast with converters_us_income_tax or other tax tools.

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?

The description states the topic but gives no when-to-use guidance, prerequisites, or alternatives. An agent must infer that this is for state-level income tax rather than federal income tax, sales tax, or other sibling calculators.

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

All FreeDailyPro Tools 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