Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-fiscal-quarter

Fiscal Quarter: Computes fiscal quarter, month and fiscal year for a date given a configurable fiscal start month 🆓 5 free trial calls per signed wallet

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "x402-fiscal-quarter"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo
startMonthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / date / description
      Removed value: -"Date to process"
    • removedInput schema / properties / startMonth / description
      Removed value: -"StartMonth to process"
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It discloses a pricing/trial detail ('5 free trial calls per signed wallet') but says nothing about defaults (e.g., what startMonth defaults to when omitted), input formats, or output shape for a computation tool.

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 delivers purpose and parameters efficiently; the trailing promotional clause about free trial calls is the only non-essential content. Nothing is buried.

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?

For a two-parameter date computation with no annotations and no output schema, the description is adequate but thin: it never defines accepted input formats or the shape of the returned fiscal fields, which an agent would need to call and interpret it reliably.

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 0%, so the description must compensate. It does semantically cover both parameters ('a date', 'a configurable fiscal start month'), which is more than the schema offers, but gives no format details such as ISO date syntax or whether startMonth is a number 1-12 or a month name.

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 ('Computes') and the resources produced (fiscal quarter, month, fiscal year) for a date with a configurable fiscal start month. It is clear what the tool returns, though it does not explicitly differentiate itself from near-siblings like x402-fiscal-year or x402-quarter-of-year.

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 when-to-use or when-not-to-use guidance is given, and no alternative is named. The phrase 'given a configurable fiscal start month' hints at a configuration scenario but never says when to pick this over x402-fiscal-year, x402-quarter-of-year, or x402-quarter-start.

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.