Skip to main content
Glama

Carpedia

by br.com.carpedia
OverviewAdmin

Quota e saldo da conta

carpedia_consumo
Read-onlyIdempotent

Uso, quota e SALDO da CONTA que está conectada: requisições do mês, limite do plano, quando reseta, saldo_milesimos (crédito pré-pago em MILÉSIMOS de real — 1000 = R$ 1,00) e preco_consulta_milesimos (o que cada consulta ACIMA da franquia custa desse saldo). Sem ferramenta MCP para criar ou aumentar saldo — reposição de crédito acontece fora deste servidor, pelo painel (/desenvolvedores/painel) ou pela API v1 (POST /api/v1/creditos). Acabando o saldo com a franquia estourada, as consultas passam a devolver 402. É sobre o consumo da API, NÃO sobre consumo de combustível do veículo. requisicoes_usadas: null significa medição indisponível no momento, não zero; preco_consulta_milesimos: null significa plano que não debita saldo (acima da franquia ele recusa, não cobra).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Adds details about null field meanings, 402 error when balance exhausted, and that it's API consumption not fuel. Annotations already indicate read-only and idempotent, but description enriches behavior context.

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?

Description is moderately long but each sentence adds useful context; no fluff or redundant padding.

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?

Covers all needed info: purpose, field semantics, null handling, error behavior, and external credit process. Sufficient for this simple read-only tool.

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?

No parameters exist; the schema is empty, so the description does not need to add parameter information. Baseline for 0 params is 4.

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?

Clearly states it returns usage, quota, and balance of the connected account. Specifically distinguishes from vehicle fuel consumption and other tools.

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?

Explains it is read-only, notes that no MCP tool exists for credit top-up, and implies when to check quota. Provides 'not for' guidance despite lacking explicit comparison to siblings.

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

All Carpedia toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources