Skip to main content
Glama
Sign In
@chartobserver/mcp-server

@chartobserver/mcp-server

by bbusche
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get recent transactions

get_recent_transactions
Read-only

List recent transactions for the configured user, including open and closed trades. Results are sorted newest first, with a configurable limit.

Instructions

List the configured user's recent transactions (open + closed, all types). Most recent first.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of transactions to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's behavioral disclosure is minimal. It adds sorting order but does not mention caching, pending transactions, or other quirks beyond annotations.

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?

Single sentence of 15 words, front-loaded with the key action and scope. No redundant information.

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 tool with one parameter and no output schema, the description covers the return type and ordering. Minor omission of default limit, though schema already specifies it.

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?

Schema coverage is 100%, and the description does not add meaning beyond the schema. Baseline 3 is appropriate.

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 verb (list), resource (transactions), and scope (configured user, recent, open+closed, all types, sorted most recent first). Distinguishes from siblings like get_open_positions and get_closed_trades.

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?

Describes what the tool does but does not explicitly state when to use it versus alternatives like get_open_positions or get_closed_trades. Sibling names provide implicit context, but no explicit guidance on when-not-to-use.

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

Deploy Server

Other Tools