DevTune MCP

devtune_get_project_usage

Read-onlyIdempotent

Read whether the project is paused and its usage: active prompts, credits spent this credit period, AI Traffic events this UTC month, and tracked pages against the page limit. Each figure carries its own period. A paused project starts no probes, agents, crawls, audits or data syncs, drops new AI Traffic, and gives credentials read access only, so writes are refused until it is resumed in the app. Its prompts and project slot do not count against the account while paused. Credits include credits held by running work until it settles. trackedPages is null until the first page-tracking status is computed. deletion gives projectDeletesAt and accountDeletesAt: when this paused project, or its lapsed team account with all its projects, will be deleted for inactivity; both are null when nothing is scheduled. Resuming the project or resubscribing cancels the deletion. Available to every credential.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 29, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantial behavioral context beyond that: paused projects start no probes/agents/crawls, drop new AI Traffic, and give read-only credentials so writes are refused. It also explains credits-held semantics, null trackedPages, and deletion scheduling fields. This is rich, non-redundant disclosure.

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?

Front-loaded with what it returns, then grouped by concern (period semantics, pause consequences, credits, trackedPages null, deletion). It is dense and fairly long, but with no output schema most sentences earn their place by defining return fields; only the deletion/resume explanation runs slightly long.

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?

Given no output schema and zero params, the description does the heavy lifting of defining return fields, per-figure periods, null conditions, and deletion semantics. An agent has everything needed to interpret the response 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?

Zero parameters, so the schema does no heavy lifting and there is nothing to mis-document; baseline is 4. The description instead spends its budget explaining return-field semantics, which is the correct trade-off for a parameterless read.

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?

The description names a specific verb (read) and enumerates the exact resource state and figures returned: pause status, active prompts, credits spent, AI Traffic events, tracked pages vs limit. This is far more than a restatement of the name and lets an agent know precisely what it gets.

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

Usage Guidelines3/5

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

There is no explicit 'when to use this vs alternatives' guidance, though no sibling tool offers project usage so the risk is low. It also states availability ('Available to every credential'), which helps an agent know it can always call it, but beyond that the usage context is implied rather than stated.

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

All DevTune MCP 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.

Resources

Need Help?