Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_get_last_week_daily_profit

Retrieve daily profit/loss for the past week from Nobitex, or switch to a 30-day view by setting monthly; use it to review recent account performance.

Instructions

Get last week's daily profit/loss.

Args: monthly: Return the last 30 days instead of one week.

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

Input Schema

NameRequiredDescriptionDefault
monthlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description must carry the burden, and it does disclose the key traits: daily granularity, a one-week window, and a 30-day override. It omits unit/currency of the profit figure, timezone or day-boundary conventions, and whether results are per-day rows or an aggregate.

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 one-line purpose followed by a single parameter note; there is no filler. The leftover 'Args:' docstring formatting is slightly awkward but does not obscure the meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter read tool with no output schema and no annotations, the definition covers the essentials of what is fetched and over what period. It stops short of describing the shape or unit of the returned profit/loss figures, which an agent would need to interpret results.

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?

Schema coverage is 0%, but the single parameter's meaning is fully explained in prose: monthly returns the last 30 days instead of one week. This also pre-empts confusion from the misleading name 'monthly', which is not a calendar month.

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 verb and resource: retrieve daily profit/loss for the last week, with a documented switch to 30 days. It does not distinguish itself from the near-identically named sibling nobitex_get_last_week_daily_total_profit, so an agent cannot tell the two apart from the text alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to choose this over nobitex_get_last_week_daily_total_profit or nobitex_get_last_month_total_profit, nor on when the monthly flag is preferable to the dedicated last-month tool. The only conditional present is the mechanical effect of the parameter.

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