Skip to main content
Glama

Diavgis — Greek Public Procurement

by gr.diavgis

Plan, Usage and Remaining Calls

get_quota
Read-onlyIdempotent

What this API key is allowed to do right now: plan, calls used this period, calls remaining, per-minute rate, page-size and pagination caps, and when the period resets. Free — this call is not counted against the quota. Check it before starting a long job so you can size the work instead of hitting a wall mid-task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
planYes
usedYescalls consumed this period (REST + MCP share one counter)
limitNomonthly quota, null if unlimited
max_pagesYespagination depth cap; deeper pages return an error, narrow with filters instead
remainingNo
pricing_urlNo
period_resetYesISO date when used resets to 0
rate_per_minYes
max_page_sizeYes

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, and non-destructive behavior. The description adds meaningful extra context: the call is free and not counted against the quota, and it reflects the current period's allowance, which is behaviorally useful beyond the structured annotations.

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 compact sentences front-load the core purpose and returned fields, then add the free-call caveat and a relevant usage tip. Every sentence earns its place with no filler or redundancy.

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

Completeness5/5

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

The description covers what the tool returns, that it is free/non-counted, and when to invoke it, while an output schema exists to document return values. With no parameters and strong annotations, nothing essential is missing for an agent to select and call this tool correctly.

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?

There are zero parameters, and the empty input schema fully documents that, so the description is not required to explain parameter meaning. The baseline for a zero-parameter tool is 4, and the description appropriately focuses on output semantics instead.

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 clearly identifies the tool as a status/readout for the API key's plan, usage, remaining calls, rate limits, and reset time. It is immediately scoped to the API key's current quota, though it lacks an explicit verb, relying on the title and noun phrasing rather than a direct action statement.

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?

The description explicitly advises using this before starting a long job, giving a concrete scenario for when to call it. It doesn't mention alternatives or exclusions, but none of the sibling tools overlap with quota-checking, so this is clear, practical guidance.

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

All Diavgis — Greek Public Procurement 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

A4.4/5.0
Disambiguation4/5

Each tool targets a distinct concern: entity resolution, entity profiles, counterparties, rankings, spend aggregates, search, act detail, lifecycle chains, expiring contracts, and quota. Minor overlap exists between get_act and get_chain since get_act can include lifecycle chain data, but the descriptions make the intended primary use clear.

Naming Consistency4/5

All names use snake_case and most follow a verb_noun pattern like find_entity, get_entity, search_tenders, and rank_entities. A few tools such as entity_counterparties and expiring_contracts are noun-phrase names, and spend_by_cpv uses a different structure, so the pattern is mostly consistent but not uniform.

Tool Count5/5

Ten tools is well-scoped for a Greek public procurement data API: the count is large enough to cover discovery, search, entity analytics, spend analytics, lifecycle detail, and quota management without feeling bloated. Each tool appears to earn its place with no obvious redundant duplicates.

Completeness5/5

The tool surface covers the full read-only procurement workflow: resolve names to tax IDs, profile entities, find counterparties, rank entities, search tenders with filters, inspect individual acts, follow lifecycle chains, monitor expiring contracts, and aggregate spend by CPV. There are no major missing operations for the stated purpose.

Resources