Skip to main content
Glama
SlothyAfk

finance-pulse

Everything about one symbol

get_symbol
Read-onlyIdempotent

Retrieves a full profile for one company or entity by ticker code, including sentiment, topics, storylines, related entities and recent statements. Use it first to see what is happening with a symbol.

Instructions

One company or other entity in a single call. Use first for "what is going on with X".

Returns who it is (name, kind, exchange); its mentions, topics, distinct sources, sentiment counts and score for the last 24 hours (d), the last 7 days (w) and all the history the plan includes, with the change against the period before and the counts over statements that name only this entity (mentions_single, score_single); the sectors of its statements; its largest topics; its storylines with the most mentions lately; the entities it shares topics with (related, empty for a rarely mentioned symbol); and its newest statements. A period without any mention is left out of periods. more_statements says whether the symbol has more statements than shown. If you expect to need them, ask for statements at its maximum: only then is statements_cursor set, and search_statements(symbol=..., cursor=...) continues exactly after them. With fewer, the cursor is null and search_statements(symbol=...) starts again at the newest, repeating the ones shown here. Do not guess a code: a wrong one costs a request. Look it up with find_symbol.

Input Schema

NameRequiredDescriptionDefault
codeYesTicker or entity code, e.g. NVDA. Non-US tickers carry an exchange suffix (0700.HK). When unsure of the code, call find_symbol first.
topicsNoHow many of its largest topics to include
statementsNoHow many of its newest statements to include

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.1

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses important behavior: omitted empty periods, more_statements, the conditional statements_cursor, related being empty for rarely mentioned symbols, and the cost of guessing a code. These details materially affect how an agent invokes and interprets the 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?

The description is front-loaded with purpose and then structured around returns and continuation behavior. It is fairly long, but most sentences carry necessary information because there is no output schema; the density is justified, though some return-field enumeration could be tightened.

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

Completeness5/5

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

For a complex entity-overview tool with no output schema, the description is highly complete: it explains the profile, time-window sentiment, topics, sectors, storylines, related entities, statements, empty-period behavior, and cursor semantics. An agent has enough context to call it correctly and understand the response shape.

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 coverage is 100%, so the schema already documents code, topics, and statements. The description still adds meaningful semantics by explaining that only requesting statements at its maximum sets statements_cursor and enables exact continuation, and by reinforcing code lookup via find_symbol when unsure.

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 states a specific resource and scope: 'One company or other entity in a single call' and positions it as the first stop for 'what is going on with X'. It then enumerates exactly what is returned, making the tool's purpose unambiguous and distinguishable from lookup-oriented siblings like find_symbol.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says to use this first for entity overview questions, warns against guessing a code and routes to find_symbol, and explains how to continue with search_statements using the returned cursor. These are concrete when-to-use and alternative-tool instructions, not implied guidance.

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