Skip to main content
Glama

MatLogica Demo

demo_advance_market

Save an advanced valuation date with supplied fixings. Each product still needs dated-state qualification.

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>",
      "dated_case": "<dated_case>",
      "idempotency_key": "<idempotency_key>",
      "guest_session": "<guest_session>"
    },
    "name": "demo_advance_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
market_idYes
dated_caseYes
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

C2.4/5.0
Behavior2/5

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

Annotations already establish write, non-destructive, closed-world, so "Save" is consistent and adds nothing new. Beyond that, the description does not say what happens on a stale market_version, how idempotency_key deduplicates retries, whether prior fixings are merged or replaced, or what a successful save returns — all material for a mutation with 12,000-item fixings arrays.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the action front-loaded, so it is not bloated. However, the second sentence is vague enough that it consumes space without conveying actionable meaning.

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?

Five required parameters, nested $defs, 20% schema coverage, no output schema, and no annotations covering concurrency or idempotency behavior — the description is far too thin for a mutation of this complexity.

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% (guest_session is the sole documented parameter), so the description must compensate and largely fails. It alludes to valuation_date and fixings, but says nothing about market_version as a concurrency guard, idempotency_key retry semantics, or market_id scoping.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Save an advanced valuation date with supplied fixings" gives a verb and a resource, but the domain jargon ("advance", "dated-state qualification") leaves it unclear how this differs from demo_create_market or demo_replace_market. An agent can guess it mutates a market's valuation date but cannot confidently distinguish it from sibling mutation tools.

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?

There is no explicit when-to-use, when-not-to-use, or named alternative. The trailing clause "Each product still needs dated-state qualification" gestures at a prerequisite but is too cryptic to act on, and nothing tells the agent when to prefer this over demo_create_market or demo_prepared_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