Skip to main content
Glama

get_build_with_ai_status

Read-only

Whether the coach can use Build with AI (Coach Pro), their remaining AI credits, and the credit price of each build kind.

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_build_with_ai_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered structurally. The description adds real value by disclosing the exact payload contents (eligibility flag, credit balance, price per build kind), which is the behavior an agent needs in order to interpret the response; it does not cover what 'credits' mean, their units, or whether the values are cached or live.

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?

A single compact sentence with no filler, and the most decision-relevant fact (can the coach use the feature) is front-loaded. The parallel 'their remaining... and the credit price of...' construction is slightly compressed but still parseable.

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

Completeness4/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 carries the return-value burden, and it does enumerate all three returned fields. Given zero parameters and a read-only status shape, this is close to complete; only formatting details of the credit values are left implicit.

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 and the schema is empty, so there is nothing to disambiguate. Baseline for a 0-parameter definition applies; nothing in the description is missing on this axis.

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 names the resource (Build with AI / Coach Pro) and enumerates three concrete facts returned: eligibility, remaining AI credits, and per-build-kind credit price. That distinguishes it from mutation siblings like start_build_with_ai and get_ai_build_job, though it is phrased as a noun clause with no verb and never states 'returns'/'reports'.

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?

No explicit when-to-use, when-not, or named alternative. The content ('whether the coach can use Build with AI', 'remaining AI credits') strongly implies the pre-flight check before start_build_with_ai, but the agent must infer that gating role rather than read it.

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.