Diavgis — Greek Public Procurement

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

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`plan`	Yes
`used`	Yes	calls consumed this period (REST + MCP share one counter)
`limit`	No	monthly quota, null if unlimited
`max_pages`	Yes	pagination depth cap; deeper pages return an error, narrow with filters instead
`remaining`	No
`pricing_url`	No
`period_reset`	Yes	ISO date when used resets to 0
`rate_per_min`	Yes
`max_page_size`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026

changedOutput schema / properties / plan / enum

Previous value: -[
-  "free",
-  "pro",
-  "business"
-]New value: +[
+  "free",
+  "basic",
+  "pro",
+  "business"
+]

AddedAug 29, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds a genuinely non-obvious behavioral fact not in the annotations: the call is free and excluded from quota accounting. It stops short of describing freshness/latency or error behavior, so it is strong but not exhaustive.

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?

Three tight sentences, front-loaded with what is returned, then cost, then the recommended call timing. Every sentence carries distinct information with no repetition of the title or schema.

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?

A no-parameter, read-only introspection tool with an output schema already describing the returned fields; the description need not restate returns. What an agent needs — what it gets, that it is free, and when to call it — is fully covered.

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 the schema-description baseline of 4 applies; there is nothing parameter-level for the description to clarify or compensate for.

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 precise verb+resource (get the API key's quota) and enumerates the exact payload: plan, calls used/remaining, per-minute rate, page-size and pagination caps, and reset timing. No sibling tool (entity/contract/tender lookups) touches quota, so the boundary is unambiguous.

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

Usage Guidelines5/5

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

Gives explicit, actionable timing: 'Check it before starting a long job so you can size the work instead of hitting a wall mid-task.' It also removes the usual hesitation about calling a meta-tool by noting the call is free and not counted against quota.

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 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.