Skip to main content
Glama
Sign In

Risk Desk

by com.avidquant
OverviewDiscussionsAdmin

risk_desk_status

Read-onlyIdempotent

Check the Risk Desk data mode, the public example, the size limits and the sign convention before requesting any figure. No market data feed, no broker connection and no hosted XVA exist.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, openWorldHint=false, destructiveHint=false). The description adds environment facts not in the annotations: there is no market data feed, no broker connection and no hosted XVA, which sets expectations about the limits of the whole server. Minor gap: it does not say whether the status can change between calls or how limits are expressed.

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 sentences, front-loaded with the action and the timing constraint, followed by a scope disclaimer. Every sentence earns its place. The only friction is the comma-heavy clause listing four things to check, which reads slightly run-on.

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?

An output schema exists, so return-value explanation is not required. Combined with the descriptions of the environment limitations and the 'before requesting any figure' trigger, an agent has what it needs to decide when and why to call a parameterless status endpoint.

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 baseline is 4. Nothing in the description is needed to clarify inputs, and it does not waste words pretending otherwise.

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 names a specific resource to inspect — Risk Desk data mode, example dataset, size limits and sign convention — which is clearly a configuration/status read rather than a computation. It is distinguishable from the quantitative siblings by framing itself as a precondition check, though the phrasing 'Check the Risk Desk data mode' is slightly abstract about what is actually returned.

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?

It gives an explicit sequencing instruction: call this 'before requesting any figure'. That tells the agent exactly when this tool belongs in a workflow. It stops short of stating when it is unnecessary (e.g. if state is already known) or naming specific sibling tools to precede.

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

All Risk Desk 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