Skip to main content
Glama
525,426 tools. Updated 2026-09-06 20:50

"Sony" matching MCP tools:

  • Comparison set for one company across KR / US / TW / JP: the company plus its closest peers, chosen from the same industry group (SIC / KSIC / TWSE / EDINET classification, normalised to one shared bucket) and ranked by market-cap proximity with same-market names first. Falls back to pure size peers when the company has no classification. Also returns the company's business-segment revenue split where available (currently Japan, from 有価証券報告書 XBRL) — informational, not yet used for ranking. Args: - company: US ticker ('AAPL'), KR 6-digit code ('005930'), TW/JP 4-digit code ('2330', '7203'), or a company name (local or English). - market: 'kr'|'us'|'tw'|'jp'|'eu' (optional) — disambiguates codes/names shared across markets (TW and JP both use 4-digit codes; 'eu' companies are addressed by ISIN). - limit: 1-10 peers (default 5). - same_market_only: true = restrict peers to the company's own market (default false — a KR chipmaker can sit next to a US one). - rank: 'size' (default) = same industry group, nearest by market cap (or revenue where there is no price feed); 'segments' = rank by business-mix similarity — each company's segment revenue shares are mapped to standard industries (companies without segment data count as 100% their own industry) and compared by cosine similarity, ties broken by size. Conglomerates (Sony: games/music/pictures/electronics/finance) then get conglomerate peers instead of whichever single bucket they were filed under. - response_format: 'markdown' (default) or 'json'. Returns: {company:{name, name_en, market, ticker|code}, basis:'sector'|'size'|'segments', sector:{group, label, name}, industry_mix:{vector:{industry:share}, primary:[industry], from_segments:bool} (rank='segments' only), peers:[{name, name_en, market, ticker|code, market_cap, per, pbr, roe, rev_cagr_3y, rs_pctile, ret_120d, similarity?, primary_industry?, has_segments?}], segments:{fiscal_year, rows:[{segment, kind, revenue_external, share_pct}]}, notes}. Examples: - {company:'7203'} -> Toyota + transportation-equipment peers, with its Automotive / Financial Services segment split - {company:'005930', same_market_only:true} -> Samsung Electronics + KR tech-hardware peers only - {company:'6758', rank:'segments'} -> Sony ranked against other multi-segment conglomerates by business mix Use when: building a comparison table or choosing competitors for a financial comparison. Don't use for strategy screens (screen_*) or for full financial statements (get_dart_financials / get_edgar_financials). Notes: company-level classification only; segment names may be geographic (Japan/Asia/USA) when a company defines its reportable segments by region. Market cap is in the company's listing currency, so cross-market rank by proximity is approximate. Revenue-proximity fallbacks (no market cap: JP, EU) convert revenue to EUR with ECB daily rates first, so mixed-currency European filers rank sensibly. Errors: unknown/ambiguous company -> candidate list; no classification -> basis='size' with a note.
    ConnectorAPI key
  • Comparison set for one company across KR / US / TW / JP: the company plus its closest peers, chosen from the same industry group (SIC / KSIC / TWSE / EDINET classification, normalised to one shared bucket) and ranked by market-cap proximity with same-market names first. Falls back to pure size peers when the company has no classification. Also returns the company's business-segment revenue split where available (currently Japan, from 有価証券報告書 XBRL) — informational, not yet used for ranking. Args: - company: US ticker ('AAPL'), KR 6-digit code ('005930'), TW/JP 4-digit code ('2330', '7203'), or a company name (local or English). - market: 'kr'|'us'|'tw'|'jp' (optional) — disambiguates codes/names shared across markets (TW and JP both use 4-digit codes). - limit: 1-10 peers (default 5). - same_market_only: true = restrict peers to the company's own market (default false — a KR chipmaker can sit next to a US one). - rank: 'size' (default) = same industry group, nearest by market cap (or revenue where there is no price feed); 'segments' = rank by business-mix similarity — each company's segment revenue shares are mapped to standard industries (companies without segment data count as 100% their own industry) and compared by cosine similarity, ties broken by size. Conglomerates (Sony: games/music/pictures/electronics/finance) then get conglomerate peers instead of whichever single bucket they were filed under. - response_format: 'markdown' (default) or 'json'. Returns: {company:{name, name_en, market, ticker|code}, basis:'sector'|'size'|'segments', sector:{group, label, name}, industry_mix:{vector:{industry:share}, primary:[industry], from_segments:bool} (rank='segments' only), peers:[{name, name_en, market, ticker|code, market_cap, per, pbr, roe, rev_cagr_3y, rs_pctile, ret_120d, similarity?, primary_industry?, has_segments?}], segments:{fiscal_year, rows:[{segment, kind, revenue_external, share_pct}]}, notes}. Examples: - {company:'7203'} -> Toyota + transportation-equipment peers, with its Automotive / Financial Services segment split - {company:'005930', same_market_only:true} -> Samsung Electronics + KR tech-hardware peers only - {company:'6758', rank:'segments'} -> Sony ranked against other multi-segment conglomerates by business mix Use when: building a comparison table or choosing competitors for a financial comparison. Don't use for strategy screens (screen_*) or for full financial statements (get_dart_financials / get_edgar_financials). Notes: company-level classification only; segment names may be geographic (Japan/Asia/USA) when a company defines its reportable segments by region. Market cap is in the company's listing currency, so cross-market rank by proximity is approximate. Errors: unknown/ambiguous company -> candidate list; no classification -> basis='size' with a note.
    ConnectorOAuth
  • HOW TO CALL THIS TOOL — read before every call: Decompose the user's request into filters first. Only what's left over goes in query. STEP 1: brand name → brand filter. STEP 2: product category → category filter. STEP 3: price → min_price/max_price. STEP 4: what remains → query. BAD: query='Sony headphones under £200' | GOOD: brand='Sony', category='Headphones', max_price=200, no query. BAD: query='tablet' | GOOD: category='Tablets', no query. BAD: query='smartwatch' | GOOD: category='Wearables', no query. BAD: query='macbook neo' | GOOD: brand='Apple', category='Laptops', query='neo'. BAD: query='Samsung QLED TV' | GOOD: brand='Samsung', category='TVs', query='qled'. If brand+category alone cover what the user wants, omit query entirely. Only put differentiating terms in query: model lines (neo, ultra, oled), variants, model numbers (WH-1000XM5, s25 ultra). CROSS-CATEGORY NOTE: Gaming headsets → category='Headphones', query='gaming headset'. The Gaming category is consoles/controllers/accessories only. Always set lite=true. If 0 results, broaden the query or drop filters. Use get_product for full specs. Search 26,000+ deduplicated UK electronics products across 7 retailers with price comparison. Covers: Laptops, Desktops, Phones, Tablets, Headphones, Monitors, TVs, Cameras, Keyboards, Mice, Speakers, Gaming, Wearables, Printers, Networking, Storage, Audio, Drones, Cables & Chargers. All prices in GBP. Returns summary data: title, brand, price, availability, category, purchase link, offer_count. MANDATORY PRICE COMPARISON: For any product relevant to the user's needs, if offer_count > 1, you MUST call get_product before responding — never mention multiple offers without presenting the full comparison. A response is incomplete if it references offer_count > 1 without retailer pricing details. Show: cheapest retailer, all other prices with the difference, exact savings amount, delivery differences if relevant. The offers[] array is sorted cheapest first. Even when the user doesn't explicitly ask about price, if offer_count > 1 it's always worth mentioning the savings. For spec-based queries (RAM, ports, screen size, weight etc.), search first then call get_product on top 3-5 results — do not assume specs from titles. STOCK: When availability is out_of_stock, mention it as an alternative and suggest checking back — do not silently omit it.
    ConnectorNo auth
  • Set the salutation, message, footer/from line, and font for a pending ecard draft. Only set footer when the sender name is known from the prompt; if missing, ask for the From name before calling this tool. Recipient details are handled later on the website.
    ConnectorNo auth
  • Final MCP handoff step. Return preview data and a Personalise Your Ecard URL. Do not collect recipient email, discuss payment in MCP, or ask the user to type continue; show the previewUrl immediately so the user can review and complete the ecard on the website.
    ConnectorNo auth
  • Select an audio track for a pending ecard draft. Call this before generate_preview whenever the chosen card has available music; choose the best matching track from the card's availableMusic list. Recipient details are handled later on the website.
    ConnectorNo auth

Matching MCP Servers

  • F
    license
    Not graded
    quality
    D
    maintenance
    Enables control of Sony TVs via IRCC remote commands through Model Context Protocol.
    -

Matching MCP Connectors

  • Browse published ecards by category, keyword, and tags. Multi-word keywords or tags are split into individual terms for tag matching, so search concepts like sympathy and loss separately instead of relying on exact phrase tags.
    ConnectorNo auth