get_license_status reports how this server is licensed and, under metered licensing, how much has been consumed. On this server it matters more than most: evaluation mode truncates every metadata read to five properties. Example prompt: “Is the metadata server licensed?”
Tool description (as the AI agent sees it):
Returns how this MCP server is licensed, and — under metered licensing — how much has been consumed. Call this when the user asks about licensing, evaluation limitations, metered usage, remaining credit, or which product engine version is running. Returns a JSON object with mode (“evaluation”, “licensed” or “metered”), licensed (true for both licensed and metered), consumption (null unless metered; otherwise quantity and credit, or error if the reading failed), and server / engine name and version. Takes no arguments and never modifies anything.
Parameters
None.
Example call
{"name":"get_license_status","arguments":{}}
Result
A JSON object describing the active licensing mode.
Evaluation mode — nothing configured:
{"mode":"evaluation","licensed":false,"server":{"name":"GroupDocs.Metadata.Mcp","version":"26.9.0"},"engine":{"name":"GroupDocs.Metadata","version":"26.6"},"note":"No license configured — output may carry evaluation limitations. ..."}
The full note text names the variables to set: GROUPDOCS_METERED_PUBLIC_KEY and GROUPDOCS_METERED_PRIVATE_KEY for metered licensing, or GROUPDOCS_LICENSE_PATH for a license file.
MCP server version and the underlying GroupDocs.Metadata engine version
note
Why licensing did not end up where you asked — present only when something needs attention
On this server "mode": "evaluation" has a sharp consequence: only the first five document properties are readable, so every read is silently truncated. See Licensing.
Example prompts
“Is the metadata server licensed?”
“How much metered credit have I used?”
“Which GroupDocs.Metadata engine version is running?”
Was this page helpful?
Any additional feedback you'd like to share with us?
Please tell us how we can improve this page.
Thank you for your feedback!
We value your opinion. Your feedback will help us improve our documentation.