Skip to main content
Glama
trading-crew-mcp

trading-crew-mcp

get_drawing

Retrieve points, color, and width for one chart drawing by ID to inspect or reuse annotations.

Instructions

Points, colour and width of one drawing by id.

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": {
      "id": "<id>"
    },
    "name": "get_drawing"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about read-only semantics, behavior when the id is unknown, or rate/limit constraints. It only hints at the return payload, which is the one useful signal it adds.

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?

One compact sentence with no filler, and the key information (what is returned, keyed by id) is front-loaded. Brevity tips into under-specification rather than padding.

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 one-parameter read tool with no output schema, the description covers the essentials: it hints at the returned fields and the lookup key. It stops short of stating read-only nature or failure behavior, which an agent would need when driving this without annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required parameter with 0% schema description coverage; the schema gives only type string. 'by id' tells the agent the string is the drawing identifier, which is meaningful added context, but the id format or source (e.g., from list_drawings) is not clarified.

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 specifies the resource (one drawing), the lookup key (by id), and the fields returned (points, colour, width), which makes it distinguishable from list_drawings or clear_drawings. It is a noun fragment rather than a verb phrase, but the retrieval intent is unambiguous.

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 statement of when to use this tool versus list_drawings (to enumerate) or clear_drawings (to remove), and no prerequisites or exclusions. The agent must infer that this is the single-item fetch.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.