Skip to main content
Glama

TILLA - market data on one clock

Plan and budget

tilla_usage
Read-onlyIdempotent

The caller's plan and budget right now: tier, history days, limits, used today. Needs your API key (hosted: the X-API-Key header; local: TILLA_API_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": "tilla_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description adds genuine value by disclosing the auth requirement and exactly how the key is supplied in hosted (X-API-Key header) versus local (TILLA_API_KEY) modes. It does not mention whether this call itself counts against the reported limits, which is the main remaining behavioral gap.

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

Conciseness5/5

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

Two sentences, front-loaded with the payload description and followed by the auth prerequisite. No filler, no restatement of the title.

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?

With no output schema and no parameters, the description correctly compensates by listing the returned fields and the auth mechanics. It could go slightly further by noting whether calling this endpoint is itself metered or rate-limited, which matters for a quota-inspection 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-arg tool applies. No parameter meaning is missing.

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?

States a specific resource ("the caller's plan and budget") and enumerates the returned fields (tier, history days, limits, used today), so the agent knows exactly what it gets. It does not explicitly differentiate from look-alike siblings such as tilla_tiers or tilla_status, so it falls short of a 5.

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?

"Right now" implies this is the current-state quota check rather than a catalog listing, which weakly points away from tilla_tiers, but no when-to-use or when-not-to-use guidance is given and no sibling is named. Usage is inferable rather than stated.

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.