Skip to main content
Glama

ADS Beast

client_market_simulation_request

Ask for a multi-agent market simulation for a client. It is queued as a request a person confirms, because it costs model usage.

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": {
      "requirement": "<requirement>",
      "client_id": "<client_id>"
    },
    "name": "client_market_simulation_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYes
requirementYesWhat to simulate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

The annotations only declare readOnlyHint=false, openWorldHint=true, destructiveHint=false — a generic write profile. The description adds genuinely useful behavior: the call does not run the simulation itself, it enqueues a request that a human must confirm, and it consumes model usage. It stops short of describing what is returned (a request ID? a status?) or expected latency.

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 with no filler. The key constraint — human-confirmed queue and model cost — is placed immediately after the purpose statement, so it is front-loaded for a scanning agent.

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?

For a simple two-parameter tool with no output schema, the description covers purpose and the async/confirmation model, which is the main thing an agent could get wrong. It is still incomplete about the undisclosed client_id parameter and about what the caller receives back after enqueueing.

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 50% — only 'requirement' is documented ('What to simulate'), while 'client_id' has no description. The description text adds nothing about either parameter (no format, no scope, no warning about which client the simulation runs against), so it fails to 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 names a specific verb ('ask for') and a specific resource ('multi-agent market simulation for a client'), which is far more informative than the bare tool name. It does not explicitly contrast with the similarly named sibling client_market_simulation, so an agent must still infer the difference, keeping it below 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?

By saying the work is 'queued as a request a person confirms, because it costs model usage,' it implicitly signals when this path is appropriate (expensive, human-gated work). However, it never states when to prefer the direct simulation or analysis siblings, nor does it state any exclusions.

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.