Skip to main content
Glama

Vat

by io.github.pipeworx-io

List Vat Formats

list_vat_formats
Read-onlyIdempotent

List the supported countries and their VAT-number formats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
  2. First observed

TDQS

A3.6/5.0
Behavior2/5

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

The description does not add behavioral context beyond the annotations, which already declare the tool as read-only, non-destructive, and idempotent. No additional traits like return format or rate limits are disclosed.

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, direct sentence with no unnecessary words. It efficiently conveys the tool's purpose.

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

Completeness4/5

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

Given there are no parameters, no output schema, and the annotations cover safety, the description is adequate. However, it could hint at the output structure (e.g., a list of country codes and patterns) to be more complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the description does not need to add parameter semantics. The base score of 4 applies as per the guideline for 0 parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists supported countries and their VAT-number formats. The verb 'list' and resource are specific and unambiguous. It distinguishes itself from sibling tools like list_subscriptions by focusing on VAT formats.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of when not to use it, prerequisites, or context for its application.

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

All Vat toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

Several tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route questions to the same underlying catalog, and ask_pipeworx_beta is currently identical to ask_pipeworx. ai_visibility_check and scan_competitor_ai_presence also overlap, and entity_profile vs recent_changes cover similar ground. The descriptions are detailed, but an agent would frequently struggle to pick the right tool.

Naming Consistency3/5

All names use snake_case, but the pattern is inconsistent: some are verb-first (validate_vat, list_vat_formats, resolve_entity), some are noun-first (entity_profile, polymarket_edges, recent_alerts), and some are product-branded (ask_pipeworx, pipeworx_feedback). It's readable but does not follow a single predictable verb_noun convention.

Tool Count2/5

33 tools is well beyond the 25+ threshold for a coherent set, especially for a server named 'Vat' where only two tools (list_vat_formats, validate_vat) relate to the apparent purpose. The bulk forms a broad data-research platform that would be more appropriately split into separate VAT and Pipeworx servers.

Completeness4/5

For the actual data-research domain, coverage is strong: discovery, single lookup, grounded answers, deep multi-source research, entity resolution, comparisons, claim verification, memory, subscriptions, and prediction-market tooling are all present. The only clear gap is that the VAT-specific surface is minimal (format validation only, no registration/VIES check), but the overall functional surface is otherwise quite complete.

Resources