Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

stock_daily

Read-onlyIdempotent

Retrieve daily stock price history from Alpha Vantage for a given symbol to support market analysis and trend tracking.

Instructions

Get daily stock price history from Alpha Vantage.

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": {
      "symbol": "<symbol>"
    },
    "name": "stock_daily"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes
api_keyNo
outputsizeNocompact or full

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the description needed to add what they can't: Alpha Vantage's aggressive call limits, the api_key requirement, or how far back 'full' history goes. It only names the provider, adding almost nothing beyond structured fields.

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?

A single tight sentence with no filler, front-loading the resource. It is efficient but so terse that the brevity costs information rather than buying clarity.

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?

For a three-parameter external-API tool with only 33% schema coverage, an undocumented api_key, an unexplained compact/full enum, and no output schema, the description omits too much to call it correctly without trial and error.

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 coverage is 33%: only outputsize has a description, and it merely echoes its own enum values. symbol and api_key are completely undocumented, and the description supplies no meaning for any of them, leaving the agent to infer that api_key is effectively required despite not being in the required list.

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?

States a specific verb and resource (get daily stock price history) plus the data source, Alpha Vantage. The word 'daily' implicitly separates it from stock_intraday, but it never names or contrasts with stock_quote, stock_intraday, or crypto_daily, so sibling differentiation is left to inference.

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 when-to-use guidance, no mention of how this differs from stock_quote (latest price) or stock_intraday (intraday bars), and no prerequisites such as an API key or rate limits. The agent must guess which stock tool fits a given request.

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

Deploy Server

Other Tools