Skip to main content
Glama
Sign In
tezga-mcp

tezga-mcp

by GoSimple-agency
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Okruženje i poreske oznake

tezga_okruzenje

Retrieve the account environment (production, sandbox, simulation) and tax labels before issuing invoices, so you know whether a receipt will be real at the tax authority.

Instructions

Vraća okruženje naloga (produkcija, sandbox ili simulacija) i poreske oznake. Pozovi OVO prvo da znaš da li bi izdavanje računa napravilo pravi račun kod Poreske uprave.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden, and it does disclose the one behavior that matters: in production the downstream consequence is a real invoice at the tax authority. "Vraća" implies a read, but read-only status, auth requirements and rate limits are not explicitly stated.

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?

Two sentences, the return content first and the call-first directive second, with no filler. Every clause carries either scope or an action rule.

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?

With no output schema, the description supplies the environment value set but leaves "poreske oznake" (tax labels) undefined as to shape and possible values. Still, for a zero-parameter preflight check the essentials an agent needs before calling are present.

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 takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies.

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?

States a specific verb and resource: it returns the account environment (production, sandbox or simulation) and tax labels. The enumerated environment values make the return semantics concrete and let an agent tell this apart from the invoice-issuing siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Pozovi OVO prvo" gives an explicit ordering instruction and the reason behind it: to learn whether issuing an invoice would hit the real Tax Administration. It does not name a specific alternative tool, but the sequencing condition is unambiguous.

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

Deploy Server

Other Tools