Skip to main content
Glama
trading-crew-mcp

trading-crew-mcp

screenshot

Captures the open TradingView Desktop window as a PNG and returns the saved file path.

Instructions

Save a PNG of the TradingView window and return the file path.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses that a file is written and that a path is returned, but says nothing about where the file lands by default, whether existing files are overwritten, what format/name the path takes, or what happens on failure. For a filesystem-writing tool with zero annotation coverage, these are meaningful gaps.

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?

One short sentence, front-loaded with the action and resource, with the return value appended. There is no filler or redundancy.

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 one-optional-parameter tool with no output schema, the description covers the action and the return type adequately. However it leaves the only parameter and the file-write behavior undocumented, which is enough of a gap to keep it at minimum viable rather than complete.

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 single optional parameter 'dir' is never mentioned in the description. With low coverage the description must compensate, but it provides no meaning for the parameter (e.g., whether it is an output directory, absolute vs relative, or the default location).

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 ('Save a PNG of the TradingView window') plus the return value ('return the file path'). It is unambiguous and no sibling tool in the list performs a screenshot capture, so no explicit differentiation is needed.

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?

Usage is only implied: an agent can infer this is for capturing a visual of the current chart window. There is no explicit when-to-use guidance, no mention of prerequisites (chart must be open/loaded), and no alternatives cited.

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