Skip to main content
Glama

MatLogica Demo

demo_market_factors

Read-only

List exact shockable factors and raw input units in your selected market version.

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>",
      "guest_session": "<guest_session>"
    },
    "name": "demo_market_factors"
  }
}

Input Schema

NameRequiredDescriptionDefault
market_idYes
guest_sessionYesWorkspace returned by demo_start_session in this conversation.
market_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is clear without the description. The description adds useful scope by saying the factors are tied to the selected market version and returns exact shockable factors and raw input units, but it does not mention session requirements or output shape.

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?

The description is a single front-loaded sentence with no redundant wording. Every phrase contributes to identifying the returned factors and their units.

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

Completeness3/5

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

There is no output schema, so the description must carry return-value detail; it does so only at a high level. It does not explain the factor/unit formats, whether a market must be prepared first, or how the three required parameters interact.

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 33%, with guest_session documented in the schema and market_id/market_version largely undocumented. The description hints at a selected market version but does not explain market_id semantics, version selection, or how the session parameter relates to the call, so it does not compensate for the coverage gap.

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 states a specific verb and resource: it lists shockable factors and raw input units, scoped to the selected market version. An agent can tell what the tool returns, though the definition does not explicitly distinguish it from siblings such as demo_stress_market.

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 or when-not-to-use guidance, and no alternative tool is named. The only implied usage is that this is a prerequisite read before stressing a market, but that inference is left to the agent.

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