Skip to main content
Glama
miratcan

Simsar MCP

by miratcan

get_sar

Get Parabolic SAR values to identify trailing stop levels and trend direction: bullish when price is above SAR.

Instructions

Parabolic SAR - trailing stop and trend indicator. Price above SAR=bullish.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
symbolYes
maximumNo
intervalNo1h
accelerationNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided, so description must carry full burden. It only states the basic indicator definition and a simple bullish/bearish rule, but does not disclose return format, error behavior, data source, or any side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely short, but under-specified. It does not earn its place by covering essential information about parameters or usage. More text with parameter explanations would be appropriate.

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

Completeness1/5

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

Given 5 parameters with no documentation and an output schema that is not referenced, the description is completely inadequate for an agent to select and invoke this tool correctly.

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

Parameters1/5

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

Zero schema coverage and no parameter descriptions in the text. Key parameters like acceleration, maximum, interval, limit, and symbol are not explained. The agent has no help understanding what values to provide.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly names the indicator (Parabolic SAR) and its function as a trailing stop and trend indicator, with a specific interpretation rule. This distinguishes it from the many sibling indicator tools.

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?

No guidance on when to use this tool vs alternatives. Does not mention suitable market conditions, timeframes, or limitations of the Parabolic SAR indicator.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/miratcan/simsar-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server