Skip to main content
Glama

MatLogica Demo

demo_stress_market

Save an explicit market-shock case. No price or stress P&L is calculated by this operation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "market_id": "<market_id>",
      "market_version": "<market_version>",
      "scenario": "<scenario>",
      "idempotency_key": "<idempotency_key>",
      "guest_session": "<guest_session>"
    },
    "name": "demo_stress_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
scenarioYes
market_idYes
guest_sessionYesWorkspace returned by demo_start_session in this conversation.
market_versionYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the write-but-non-destructive profile is covered. The description usefully adds that no pricing or stress P&L is triggered, but says nothing about persistence semantics, idempotency behavior, or whether an existing case is overwritten.

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 action and immediately followed by the most decision-relevant caveat. No filler or restatement of the tool name.

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

Completeness2/5

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

A 5-required-parameter mutation with a nested scenario/Shift object, no output schema (so the returned case identifier or result shape is unknown), and 20% schema coverage needs substantially more description than two sentences. Preconditions such as session binding and version pinning are left entirely to the caller's inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20% — just guest_session is documented in the schema. The description adds no meaning for market_id, market_version, idempotency_key, or the nested scenario/shifts structure, leaving four required parameters with no explanatory support anywhere.

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 ('Save an explicit market-shock case') and adds a negative scope clause ('No price or stress P&L is calculated'), which distinguishes it from pricing/valuation siblings. It does not explicitly name a contrasting sibling, so it stops short of a 5.

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 only implied: you call this when you want to persist a hand-built shock scenario rather than have the system compute one. There is no explicit 'use when X, not Y', no prerequisites (session start, required market version), and no named alternative for pricing the saved case.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources