Skip to main content
Glama

This key: exact credit balance, remaining quota, environment

keys_me
Read-only

Returns the calling key, the exact balance of the ledger behind it (balanceMicro: integer micro-credits, 1 credit = $1.00 = 1,000,000), what is left in each daily quota bucket, and the environment. No charge, and consumes no quota. (GET https://app.deepvalues.ai/api/v1/keys/me — no charge; needs a connected account or a dv_sk_ key)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations supply readOnlyHint and openWorldHint, so the safety profile is covered; the description adds relevant behavior beyond them: zero cost, zero quota consumption, authentication requirement, and the exact HTTP endpoint. It does not cover error cases (expired key, unconnected account) or rate limits, so a 4 rather than 5.

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 is returned, then cost/auth constraints. Slight redundancy: 'No charge, and consumes no quota' is restated as 'no charge' inside the parenthetical, which is the only wasted wording.

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?

For a zero-parameter, no-output-schema read tool, the description enumerates the meaningful return fields (key, balance, quota buckets, environment) and prerequisites, which is nearly everything an agent needs. The granular shape of the quota buckets and environment values is left unspecified, a minor gap.

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 baseline of 4 applies. The description still explains the unit convention for balanceMicro, which is useful semantic framing even for a no-argument 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?

Specific verb plus enumerated resources: the calling key's identity, its exact micro-credit balance (with unit conversion stated), per-bucket daily quota remaining, and environment. The phrase 'the calling key' separates it from keys_create, and the field enumeration means an agent knows what it gets 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?

Says the call is free and consumes no quota, which is an implicit green light to call it whenever balance/quota data is needed, and states the prerequisite (connected account or dv_sk_ key). It does not explicitly compare against account or credits_packs, so no exclusion guidance, but the cost-free context is clear.

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