Skip to main content
Glama

Syracuse Company News

by io.github.1145-am

stories_industry_location_list

Stories by Industry/Location Simplified endpoint that runs the same logic as the main stories endpoint, with a restricted parameter set (industry and the location the story happened in). Stories can either be

-- IndustrySectorUpdate

or activities in an organization's lifecycle. We track the following activities:

-- CorporateFinanceActivity: M&A, investments, stock purchases

-- PartnershipActivity: Partnership between 2 or more organizations. Often, companies describe their customers as their partners. This type of activity covers both genuine partnerships and customer/supplier relationships

-- RoleActivity: Key change in senior personnel, e.g. replacing CEO

-- LocationActivity: Opening or closing a new location (e.g. setting up in EMEA or shutting down a factory in a particular town)

-- ProductActivity: New product launches

-- AnalystRatingActivity: Updates from industry analysts

-- EquityActionsActivity: Stock repurchases, dividends etc

-- FinancialReportingActivity: Notice that an organization is going to announce its financials

-- FinancialsActivity: Information about company financials, e.g. revenue or EBITDA

-- IncidentActivity: Adverse incidents e.g. safety

-- LegalActivity: Lawsuits or activities that could lead to lawsuits, e.g. SEC investigations

-- MarketingActivity: e.g. launching a new advertising campaign

-- OperationsActivity: Company operations news, e.g. we are investing in a new product, or we have just completed an security audit

-- RecognitionActivity: e.g. we are delighted to announce that we won Agency of the Year

-- RegulatoryActivity: Legal or regulatory activity affecting this organizationg e.g. permit for drilling, or regulatory filing

Parameters:

  • activity_location: Location group name or id (e.g. "texas", "india", "MidWest", "FR", "us-ca") where the story happened. Not case sensitive. Accepts multiple values. They must each match an id or name from the location groups endpoint.

  • activity_location_id: Location group identifiers (e.g., "Southern Asia", "BT", "US-CA") where the story happened. Case-sensitive. Accepts multiple values. They must each match an id from the location groups endpoint.

  • include_provenance: Add a source_audit field to each story explaining how it was surfaced (source path, Typesense match score, and the entity that carried it). Defaults to false.

  • industry: Industry name to filter by. Accepts multiple values.

  • industry_context: Optional context aspects to anchor the industry search in. Pass each aspect as a separate value. Can be a broader category name or detailed examples (e.g. "Movie Industry" when searching for "Distribution", or "BOPP Film" and "BOPET Film" when searching for "Film"). Applied to every value of industry in the same request.

  • industry_id: Industry ID (topic ID) to filter by. Accepts multiple values. They must each match a topic_id from the industry-clusters endpoint.

  • location: Deprecated alias of activity_location, kept for backwards compatibility. It means the location the story happened in, not where the company is based.

  • location_id: Deprecated alias of activity_location_id, kept for backwards compatibility. It means the location the story happened in, not where the company is based.

  • output: Output format. Defaults to "simple" (SimpleStory schema). Use "full" for the detailed response.

  • page: A page number within the paginated result set.

  • page_size: Number of results to return per page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoA page number within the paginated result set.
outputNoOutput format. Defaults to "simple" (SimpleStory schema). Use "full" for the detailed response.
industryNoIndustry name to filter by. Accepts multiple values.
locationNoDeprecated alias of `activity_location`, kept for backwards compatibility. It means the location the story happened in, not where the company is based.
page_sizeNoNumber of results to return per page.
industry_idNoIndustry ID (topic ID) to filter by. Accepts multiple values. They must each match a topic_id from the [industry-clusters](#/industry-clusters/industry-clusters_list) endpoint.
location_idNoDeprecated alias of `activity_location_id`, kept for backwards compatibility. It means the location the story happened in, not where the company is based.
industry_contextNoOptional context aspects to anchor the industry search in. Pass each aspect as a separate value. Can be a broader category name or detailed examples (e.g. "Movie Industry" when searching for "Distribution", or "BOPP Film" and "BOPET Film" when searching for "Film"). Applied to every value of `industry` in the same request.
activity_locationNoLocation group name or id (e.g. "texas", "india", "MidWest", "FR", "us-ca") where the story happened. Not case sensitive. Accepts multiple values. They must each match an id or name from the [location groups](#/location-groups/location-groups_list) endpoint.
include_provenanceNoAdd a `source_audit` field to each story explaining how it was surfaced (source path, Typesense match score, and the entity that carried it). Defaults to false.
activity_location_idNoLocation group identifiers (e.g., "Southern Asia", "BT", "US-CA") where the story happened. Case-sensitive. Accepts multiple values. They must each match an id from the [location groups](#/location-groups/location-groups_list) endpoint.

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explains that include_provenance adds a source_audit field, clarifies the distinction between location (where the story happened) and company location for deprecated aliases, and details the varied activity types (e.g., M&A, product launches, legal issues) that constitute stories. It does not explicitly state read-only behavior or side effects, but the nature of a 'list' endpoint and the context provided are sufficient for typical use. No contradictions with annotations exist since none are provided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is lengthy, containing a full bulleted list of 15 activity types and a verbose parameter section that duplicates schema content. While it is organized with headers and bullet points, it could be trimmed by referencing the main endpoint's documentation for activity types and relying on the schema for parameter details. The front-loaded title and explanation are clear, but the overall verbosity reduces efficiency.

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

Completeness3/5

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

Given 11 parameters, no required fields, no output schema, and no annotations, the description provides substantial context: it defines what a 'story' is (including activity types), explains deprecated aliases, details the include_provenance option, and notes the output format options. However, it lacks details on pagination defaults (e.g., typical page_size limits), response structure beyond 'simple' vs 'full', and any error or edge-case behavior. These gaps make it incomplete for fully autonomous use without external documentation.

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 coverage is 100%, and the description's parameter section simply repeats the schema's per-parameter descriptions (including examples, case-sensitivity notes, and endpoint references). It adds no new semantic value beyond what the schema already provides, so the baseline score of 3 is appropriate. The description does group parameters and explain deprecated aliases, but these details are also in the schema.

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 explicitly states 'Stories by Industry/Location' as a 'Simplified endpoint that runs the same logic as the main stories endpoint' with a restricted parameter set for industry and location. It clearly differentiates itself from the sibling stories_organization_list by focusing on industry/location filters, and provides a comprehensive list of story activity types returned, making the tool's purpose unambiguous.

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?

The description frames the tool as a 'Simplified endpoint' with a 'restricted parameter set (industry and the location)', implying it should be used when only these filters are needed. It does not explicitly name alternative tools or provide when-not-to-use instructions, but the contrast with the 'main stories endpoint' and the emphasis on restricted parameters offer reasonable guidance. The activity type list also helps users understand what types of stories they can expect.

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

All Syracuse Company News toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: location_groups_list provides reference data for allowed location filters, register_and_get_key_create handles account creation and API keys, and the two stories endpoints are differentiated by their primary filter (industry/location vs. organization). The overlap between stories_industry_location_list and stories_organization_list is minimal and easily resolved by their names and descriptions.

Naming Consistency3/5

Three tools follow a 'noun_list' pattern (location_groups_list, stories_industry_location_list, stories_organization_list), but the fourth, register_and_get_key_create, breaks the pattern with a verbose verb sequence and a 'create' suffix. This inconsistency, while understandable, makes the set slightly less predictable.

Tool Count4/5

Four tools is a reasonable size for this server's scope, covering location taxonomy, user registration, and two story retrieval flavors. It stays within the well-scoped range, though it's on the smaller side; one or two more tools for generic story search or detail retrieval would feel even more complete but are not strictly necessary.

Completeness3/5

The server exposes two simplified story endpoints but references a 'main stories endpoint' and an 'industry-clusters' endpoint that are not provided, leaving a notable gap for agents wanting a broader search or industry taxonomy. It lacks a direct story-by-ID lookup or generic listing, so coverage is partial and may force agents to work around missing operations.

Resources