Skip to main content
Glama

audit_formatting

Audit React, React Native, Vue, and Flutter source for hardcoded currency, number, percentage, date, and time formatting, then automatically migrate issues to Intl or Flutter formatters.

Instructions

Audits project source code (React, React Native, Vue, Flutter) for hardcoded currency concatenations, unlocalized numbers (.toFixed()), raw percentage signs, and unparameterized date/time calls (.toLocaleDateString()), with automated logical migration using Intl or package:intl.

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": "audit_formatting"
  }
}

Input Schema

NameRequiredDescriptionDefault
fixNoIf true, automatically fixes formatting issues using Intl or Flutter formatters.
scopeNoOptional list of relative paths, files, or folders to limit formatting audit to.
dryRunNoIf true (default when fix is true), previews changes via unified diff without modifying files.
excludeNoOptional glob patterns of files to exclude from formatting audit.
includeNoOptional glob patterns of files to include in formatting audit.
categoriesNoCategories to audit: 'CURRENCY', 'NUMBER', 'PERCENTAGE', 'DATE', 'TIME'. Defaults to all.
projectPathNoOptional project root directory. Defaults to current working directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.6

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose what the fix does (migration to Intl / package:intl). However, it never says that a fix run modifies project source files, that dryRun previews a unified diff, or whether changes are reversible or idempotent — material for a tool that can rewrite code.

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?

A single front-loaded sentence that leads with the verb and audit scope, then ends with the remediation capability. Dense but every clause names concrete defect patterns; no filler.

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?

With 7 optional parameters, no output schema, and no annotations, the definition leaves real gaps: it doesn't say what the audit returns (findings list? per-file report?), how results are surfaced, or how the fix/dryRun interaction behaves. The defect taxonomy is complete, but the operational picture is not.

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 seven parameters including fix, dryRun, scope, include/exclude, and categories are documented in the schema itself. The description adds no semantics beyond that (it doesn't mention the categories enum or scoping), so the baseline of 3 applies.

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 states a specific verb (audits) plus concrete resources: hardcoded currency concatenations, .toFixed() numbers, raw percentage signs, and .toLocaleDateString() calls, scoped to React/React Native/Vue/Flutter. That level of detail makes the audited domain distinguishable from a generic i18n scan, though it never explicitly separates itself from siblings like audit_plurals or scan_hardcoded_texts.

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 only implied: the enumerated defect classes suggest when this tool applies, and 'automated logical migration' hints that a fix mode exists. There is no statement of when to prefer this over scan_hardcoded_texts or audit_plurals, and no prerequisites (project must be i18n-ready?) are given.

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