Skip to main content
Glama
nubiia-dev
by nubiia-dev

get_taxes

Retrieve all available taxes with pagination and field filtering. Each tax includes key, name, amount, scope, and group for document integration.

Instructions

Get all available taxes with pagination support. Supports field filtering to reduce response size. Each tax has: key (the stable identifier, e.g. "s_iva_21"/"p_iva_21" — this is the value used in a document line's taxes[]), id (mirrors key), name, amount (the percentage as a string, e.g. "21"), scope ("sales" or "purchase"), group (e.g. "iva"), and type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (starting from 1, default: 1)
fieldsNoSelect specific fields to return (e.g., ["key", "name", "amount", "scope"]). Reduces response size. If not provided, returns default fields: id, key, name, amount, scope, group, type. NOTE: the tax rate field is `amount` (not `percentage`) and the identifier is `key`.
summaryNoReturn only total count and page count without items (default: false)
pageSizeNoNumber of items per page (default: 50, max: 500)
Behavior3/5

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

No annotations provided, so description carries full burden. It describes the fields returned and pagination features but does not explicitly state that the operation is read-only, safe, or idempotent. No contradictions, but could be more explicit about non-destructive nature.

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?

Single paragraph, concise, well-structured. First sentence states primary purpose, then lists fields and parameter details. No redundant information.

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?

Covers pagination, field filtering, and all return fields. Lacks explicit mention of response structure (e.g., an array of objects with pagination metadata) but since no output schema, this is acceptable. Minor gap for a listing tool.

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?

Schema covers 100% of parameters. Description adds valuable context beyond schema: clarifies field names ('amount' vs 'percentage'), highlights that 'key' is the stable identifier for document lines, and explains the effect of 'summary' parameter. This enhances understanding.

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?

Description clearly states the verb 'Get', resource 'taxes', and key features (pagination, field filtering). It distinguishes from sibling tools by specifying the exact resource and capabilities.

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?

No explicit guidance on when to use this tool vs alternatives. However, the purpose is straightforward, and the sibling list makes it clear that this is the tool for retrieving tax definitions. Lacks when-not or alternative recommendations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nubiia-dev/mcp-holded'

If you have feedback or need assistance with the MCP directory API, please join our Discord server