Skip to main content
Glama

ADS Beast

client_market_simulation

Read-only

Status and report of the multi-agent market simulations requested for a client.

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

Input Schema

NameRequiredDescriptionDefault
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that the tool returns status and report for requested simulations, but it does not explain polling behavior, freshness, report contents, or any open-world data implications beyond the annotation.

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 a single front-loaded sentence with no filler or repetition. It is concise, though the noun-phrase form makes the intended action slightly less explicit than a verb-first phrasing.

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?

The tool has one required parameter, no output schema, and openWorld/readOnly annotations. The description says it returns status and report but does not describe the response shape or clarify client_id, so it leaves meaningful gaps for an agent trying to call and interpret it correctly.

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 0%, and the only parameter client_id has no schema description. The phrase 'for a client' weakly ties the parameter to a client identifier, but it does not explain the expected ID format, how to obtain a valid client_id, or what happens if it is omitted (though it is required).

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?

The description identifies the resource as status and report of multi-agent market simulations for a client. However, it is a noun phrase without an explicit retrieval verb and does not explicitly distinguish this read/status tool from the sibling client_market_simulation_request initiation tool.

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?

It gives no when-to-use guidance, no exclusions, and does not mention the alternative of requesting a new simulation via client_market_simulation_request. The agent must infer that this is for checking existing simulations rather than starting one.

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.