Skip to main content
Glama

MatLogica Demo

demo_price_book

Queue the selected portfolio using exact saved versions and an admitted method. Read actual per-trade kernel and timings from demo_get_job; use matching work when comparing timings.

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": {
      "book_id": "<book_id>",
      "book_version": "<book_version>",
      "market_id": "<market_id>",
      "market_version": "<market_version>",
      "settings": "<settings>",
      "idempotency_key": "<idempotency_key>",
      "guest_session": "<guest_session>"
    },
    "name": "demo_price_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
book_idYes
settingsYes
market_idYes
book_versionYes
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.9/5.0
Behavior2/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 description need not restate safety. But it does not explain what "Queue" actually does behaviorally, such as whether it starts an asynchronous job, how idempotency_key is enforced, how guest_session scopes the operation, or what failure modes exist. The behavioral burden remains largely unmet.

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?

The description is two compact sentences with the primary action front-loaded and no obvious filler. The second sentence mixes output-retrieval guidance with comparison advice, and "admitted method" is unexplained jargon, but overall it is efficient.

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?

This is a seven-required-parameter mutation/queue tool with no output schema, so the description should clarify the return value or job handle and idempotency semantics. It omits those essentials and does not compensate for the low schema description coverage, leaving an agent under-informed for correct invocation.

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 14%, so the description needs to compensate, but it only maps loosely to book_version, market_version, and settings.method through "exact saved versions" and "admitted method." It adds no meaning for seed, paths, native_threads, payoff_sharpness, or idempotency_key, leaving most parameters undocumented in prose.

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 uses a specific verb, "Queue," and resource, "selected portfolio," and ties it to saved versions and an admitted method. It also points to demo_get_job for results, which helps distinguish it from that sibling. The purpose is clear, though the jargon "admitted method" and "queue" leaves some ambiguity about what pricing actually occurs.

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?

It gives implied usage guidance by directing the agent to read actual per-trade kernel and timings from demo_get_job and to use matching work when comparing timings. However, it does not explicitly state when to use this tool versus alternatives, nor does it provide any when-not conditions.

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