Skip to main content
Glama
Sign In
cse-mcp

cse-mcp

by lxnid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Stock profile

get_stock
Read-onlyIdempotent

Retrieve a live Colombo Stock Exchange stock profile by symbol, including price, change, volume, range, highs/lows, market cap, foreign holding, and beta for market analysis.

Instructions

Full live profile of one stock: price and change, today's range and volume, week/month/YTD/52-week/all-time highs and lows, market cap, foreign holding, beta. symbol like "JKH", "JKH.N0000" or "COMB.X0000".

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": "get_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond that with 'live', signalling fresh rather than cached/settled data, and by scoping the breadth of the profile. It says nothing about error behavior for invalid tickers, latency, or rate limits, which matters for an openWorldHint tool.

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?

Two sentences, front-loaded with the core purpose and followed by a tight field inventory and the format note. The field list is dense but each item earns its place by telling the agent what coverage to expect; no filler or hedging.

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

Completeness4/5

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

For a single-parameter read tool with a full annotation set and an output schema, this is close to complete: purpose, data coverage, and symbol format are all present. The only missing piece an agent might want is a fallback for symbols that don't resolve, plus which suffix format is preferred.

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

Parameters4/5

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

Schema description coverage is 0%, so the description carries the burden for the sole parameter — and it does, giving three literal symbol formats ('JKH', 'JKH.N0000', 'COMB.X0000') that the schema never states. The mixed suffix conventions could still leave an agent unsure which form is canonical, keeping it out of the top band.

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 opens with a concrete verb and resource — 'Full live profile of one stock' — then enumerates exactly what the profile contains (price/change, range, volume, multi-horizon highs and lows, market cap, foreign holding, beta). That is far more specific than a restatement of the name. It stops short of naming a sibling, so an agent must infer from names alone that list_stocks is the multi-symbol equivalent and get_price_history the time-series one.

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: the phrase 'one stock' and the single required symbol signal this is the per-symbol lookup, which implicitly contrasts with the collection-oriented siblings. There is no explicit 'use this when…' statement, no exclusion of get_price_history for historical series, and no note about what to do if the symbol is unknown.

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