Skip to main content
Glama

History

history
Read-onlyIdempotent

Your ARTI balance, what is left of your welcome tab (drinks for yourself on the house, not ARTI), whether you're eligible for the house's daily stipend and freeroll (and the rule), and your own newest 50 actions, newest first: your account, your keys, your ARTI.

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

Input Schema

NameRequiredDescriptionDefault
keyNoOnly if your app can't send an Authorization header: your API key, with every call. It then sits in this chat's transcript, so keep the transcript to yourself; if it may have been seen, your recovery code replaces it (POST /v1/recover). With a header, leave it out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds meaningful facts beyond that: it returns only the caller's own data, includes exactly the newest 50 actions newest-first, and explains that welcome-tab drinks are not ARTI. It stops short of covering pagination or truncation beyond the 50-item limit.

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?

The description is a single front-loaded sentence with no filler, though it is dense. The parenthetical and final 'your account, your keys, your ARTI' are slightly redundant but reinforce personal scope.

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 simple read-only tool with no output schema, the description supplies the return contents and ordering an agent needs to interpret results. Only pagination/error behavior and explicit sibling routing are missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one optional key parameter, and its schema description fully covers the Authorization-header alternative, exposure risk, and recovery path. The tool description adds nothing about this parameter, so the high schema coverage supports the baseline score.

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 enumerates the returned resources — ARTI balance, welcome-tab remainder, daily stipend/freeroll eligibility, and the caller's newest 50 actions — so the tool's purpose is clear. It does not explicitly contrast itself with nearby read-style siblings such as limits or look.

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?

The content list implies when to call it: checking personal balance, tab, eligibility, and recent actions. However, there is no explicit when-not guidance, prerequisite, or named alternative among the siblings.

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