Skip to main content
Glama

Get research subjects

get_subjects

Retrieves matching released research subjects by name or kind, including companies, industries and investment themes. Returns matching subject identifiers and available research coverage. Useful for resolving a non-company topic before requesting a brief or cases. Use the returned entity_id for follow-up research and preserve ambiguity when multiple subjects match; a ticker is optional for non-company subjects. Uses account allowance or prepaid credit.

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "get_subjects"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
kindNo
as_ofNo
limitNoRequested page size. For ticker/entity belief lists, MCP returns up to twelve complete summaries within its response budget; pagination.limit is the effective size. Continue with next_cursor and the same ticker/entity_id. REST supports larger pages.
cursorNo
contextYesUser's research goal in one short sentence (max 300 characters); include relevant ticker and topic. Exclude names, contact/account/portfolio details, credentials and source text.
llm_modelYesYour model identifier, if known (e.g. gpt-6); otherwise leave unknown. Exclude credentials and private deployment names.
conversation_idNoPass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

The billing disclosure ('Uses account allowance or prepaid credit') explains why readOnlyHint is false despite the lookup-style behavior — genuinely useful context beyond the annotations. It also states the return includes entity_id for follow-up and that ambiguity should be preserved. It does not cover failure modes or rate limits, so it isn't fully transparent.

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 purpose and the primary use case are front-loaded in the first two sentences, followed by operational guidance. It is dense but every sentence carries information; slightly tighter grouping of the follow-up/ambiguity guidance would help.

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 an 8-parameter tool with an output schema, the description covers purpose, cost implication, entity_id follow-up, and ambiguity handling — the things the schema cannot say. The remaining gap is point-in-time (as_of) and paging behavior, which the limit/cursor schema text partially covers but as_of does not.

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?

With only 50% schema description coverage, the description must compensate; it clarifies that matching is by name or kind and that ticker is optional for non-company subjects, which meaningfully maps to q, kind, and entity resolution. However, as_of, cursor, and their semantics have no explanation in either place, so the coverage gap is only partly closed.

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 gives a specific verb and resource ('Retrieves matching released research subjects by name or kind') and enumerates the subject classes covered (companies, industries, investment themes). It implicitly separates itself from get_companies/get_tickers by calling out non-company subjects, though it never names those siblings outright.

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

Usage Guidelines4/5

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

It explicitly frames the use case: resolve a non-company topic before requesting a brief or cases, and keep results ambiguous when multiple subjects match. That is a clear when-to-use signal tied to named downstream tools. It lacks an explicit 'do not use this when…' exclusion, which keeps it below a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.