Skip to main content
Glama

compliance_capabilities

Read-only

Return supported compliance frameworks for a country (BAS, STP, GST, MTD, 1099, etc.) with version and certification info.

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": {
      "country": "<country>"
    },
    "name": "compliance_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesRequired ISO country code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false, so safety is covered. The description adds value beyond them by disclosing what comes back — version and certification info — which is important given there is no output schema. It does not say what happens for a country with no supported frameworks.

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?

A single front-loaded sentence with a clear verb, scope, and illustrative examples. Every clause earns its place and nothing is padded.

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?

For a one-parameter read-only lookup with full schema coverage, the description covers purpose and return contents, which compensates for the absence of an output schema. Minor gap: no statement of behavior when a country has no frameworks or whether results are static.

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 coverage is 100% with an enumerated list of eight country codes and a description marking it required, so the description need not restate formats. It adds no meaning beyond the schema for the country argument, making the baseline 3 appropriate.

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 ('Return') and resource ('supported compliance frameworks for a country') and gives concrete examples (BAS, STP, GST, MTD, 1099) that make the domain unambiguous. It implicitly separates itself from siblings like compliance_deadlines or list_tax_rates, but never names an alternative to sharpen the boundary.

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: an agent can infer it should call this to discover which frameworks a given country supports. There is no explicit when-to-use versus compliance_deadlines or country_support, and no stated exclusions or preconditions.

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.

Resources