Skip to main content
Glama
Sign In

JW3 MCP Server

by io.github.agnostic4321-ops
OverviewDiscussionsAdmin

Read risk limits

read_risk_limits
Read-only

READ-ONLY: read the user's risk posture (kill switch, autonomy level, caps, daily usage). Never edits limits — the agent must check this before proposing live size.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the 'READ-ONLY' prefix is partly redundant, but the description adds genuinely new context: the tool never edits limits and must be checked as a gating step before sizing trades. It does not describe freshness/caching of the posture data, but with annotations covering the safety profile that gap is minor.

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?

Two short clauses with the read-only constraint and the required-use case front-loaded. 'READ-ONLY:' and 'Never edits limits' partially duplicate the same point and the same annotation, which is slight waste, but otherwise every phrase carries 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?

With no output schema and a required use-before-sizing role, the description compensates by naming the four posture fields an agent will receive. It could say more about what a blocked kill-switch state means for the agent's next step, but it is sufficient to call the tool correctly.

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 the description has nothing to disambiguate and the schema-coverage signal is moot. Baseline for a parameterless tool applies; no misleading parameter guidance is present.

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?

States a specific verb ('read') and resource ('the user's risk posture'), then enumerates the contents — kill switch, autonomy level, caps, daily usage — which no sibling read tool covers. The 'Never edits limits' clause further separates it from the mutation/proposal siblings.

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

Usage Guidelines4/5

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

Gives an explicit trigger: the agent must call this before proposing live size. That is a concrete precondition rather than implied usage. It does not state any when-not-to-call condition or name an alternative for modifying limits, which keeps it below a 5.

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

All JW3 MCP Server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources