Skip to main content
Glama

Read Project Database usage

get_project_database_usage
Idempotent

Read this Project's database capacity and measured usage. It reports the installation's phase and authorization, and the installed database level only while the installation is ready; a chosen level not yet ready is reported as selected, and with nothing installed no capacity limits are reported. It also reports the database count limit, bytes per database, each database's quota, last measured usage, observation time and write suspension. Only the Project's own data counts; an empty database counts as zero. Also reports the Solo or Team plan and the daily request quota Central publishes for it: available with the published number, unlimited with no figure when Central publishes its unlimited value, unavailable when Central published nothing usable or could not be reached, or not_applicable on a deployment without Central; no per-day request usage count or remaining daily quota is available. Administrator only. Does not install, provision or purchase; returns no connection details or credentials.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations it discloses the conditional reporting logic an agent cannot infer elsewhere: a level is reported as 'selected' while not ready, nothing installed means no capacity limits, empty databases count zero, and only the Project's own data is counted. It also enumerates the four plan-quota states (available, unlimited, unavailable, not_applicable) and states plainly that no per-day usage count or remaining quota is returned. The only friction is that the description frames the tool purely as a read while annotations carry readOnlyHint=false; that default-value mismatch is worth noting but is not a direct contradiction of any stated claim.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded: the first sentence states what is read, and the exclusions and admin requirement land at the end where they belong. The middle is dense with parallel state enumerations (ready/selected, available/unlimited/unavailable/not_applicable) that each carry real information, though the long multi-clause sentences make it heavier to parse than necessary.

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?

There is no output schema, so the description must carry the return-value burden itself, and it does: it describes every reported field, the conditional states of each, and explicit absence cases (no per-day usage count, no connection details). Combined with the admin prerequisite and the zero-parameter signature, an agent has everything needed to call this and interpret the result.

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 no parameters and the schema is an empty object, so there is nothing to disambiguate; the description correctly spends no words on inputs. Baseline 4 applies for a zero-parameter tool.

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?

It names a specific verb and resource — read a Project's database capacity and measured usage — and enumerates concrete fields: phase/authorization, installed level, database count limit, bytes per database, per-database quota, last measured usage, observation time, write suspension, and plan request quota. None of the sibling names (list_users, describe_project, list_roles) could be mistaken for this, and the closing sentence rules out install/provision/purchase, so the agent can distinguish it without opening a schema.

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?

It supplies a hard prerequisite ('Administrator only') and clear non-use cases ('Does not install, provision or purchase; returns no connection details or credentials'), which steers an agent away from expecting mutations or credentials. It stops short of naming a specific alternative tool to use for provisioning or connection details, so the guidance is clear but not fully closed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources