Skip to main content
Glama
Sign In

Equibles

by io.github.daniel3303
OverviewDiscussionsAdmin

Stock Profile

GetStockProfile
Read-only

Get one listing's profile: the company's description, website, sector and industry, SEC CIK, LEI and fiscal year end, the security's ISIN and type, and the company's other listings on every covered exchange with the symbol each is read by. Pass a bare ticker for a US listing or MIC:TICKER (e.g. XETR:SIE) for one on another exchange.

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": {
      "ticker": "<ticker>"
    },
    "name": "GetStockProfile"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesTicker (e.g. AAPL, BRK-B) or MIC:TICKER for a listing on another exchange (e.g. XETR:SIE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by enumerating the returned payload, including the notable behavior that other listings are returned 'on every covered exchange with the symbol each is read by' — useful since no output schema exists. It does not say what happens for an unknown ticker or an uncovered exchange.

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 purpose and then the input format. The field enumeration is dense but each item carries information; a bulleted or grouped structure would scan better, but nothing is wasted.

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 one-parameter read tool with no output schema, the description does the necessary work by describing the returned fields and the cross-listing behavior. The remaining gap is edge-case behavior (invalid ticker, unsupported exchange), which is minor for a simple lookup.

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?

Schema description coverage is 100%, so the single ticker parameter is already fully documented in the schema, including the MIC:TICKER form and examples. The description largely restates that format rather than adding new meaning; baseline 3 is appropriate.

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?

States a specific verb and resource ('Get one listing's profile') and then enumerates exactly what that covers: company description, website, sector/industry, SEC CIK, LEI, fiscal year end, ISIN, security type, and cross-exchange listings. This is clearly distinguishable from siblings like GetFundProfile, GetEtfProfile, and GetOrganization.

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?

The description gives clear addressing guidance (bare ticker for US, MIC:TICKER for other exchanges), which implies when the tool applies, but it never states when to prefer it over neighbors such as GetOrganization or SearchListings, nor any exclusion or prerequisite. Usage is inferable rather than explicit.

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

All Equibles toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources