Skip to main content
Glama
Sign In
tas-guard

tas-guard

by intoApex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

tas_guard_status

Read-only

Reads the trading limits for this connection, today's usage, kill switch state, and pending approvals. Use it to check status before placing orders through the guard.

Instructions

TAS Guard: show the trading limits that apply to this connection, today's usage, the kill switch and pending approvals. Read-only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description's 'Read-only' is largely redundant. However, it adds genuine value with no output schema present by enumerating what is surfaced (limits, today's usage, kill switch, pending approvals), which is behavioral content beyond the 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?

Two short sentences, front-loaded with the tool name and the exact content shown, with the safety note last. Every clause carries information; nothing is padded.

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 parameters, no output schema, and read-only annotations, the only open question is what the tool returns, and the description answers that by naming the four reported areas. It stops short of describing format or freshness beyond 'today's usage', but nothing required for correct invocation is missing.

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 schema has zero parameters, which is the baseline-4 case. There is nothing further for the description to clarify, and it correctly implies the tool operates on the ambient connection rather than taking arguments.

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 gives a specific verb ('show') and an enumerated resource set (trading limits, today's usage, kill switch, pending approvals) scoped to 'this connection', which a reader can easily distinguish from get_account_info or get_orders. It does not explicitly name or contrast any sibling tool, which is what a 5 would require.

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?

Usage is implied by the content ('limits that apply to this connection'), so an agent can infer it answers a risk/limits check, but there is no statement of when to prefer it over get_account_info or when it is not appropriate. No prerequisites, timing, or exclusions are given.

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