Skip to main content
Glama

Syracuse Company News

by am.1145.syracuse

stories_organization_list

Stories by Organization Simplified endpoint that runs the same logic as the main stories endpoint, with a restricted parameter set: org_name, optionally narrowed by where the company is based (org_location), what it does (industry), and where its stories happened (activity_location). 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.

  • industry: Industry name the company must work in. Narrows which companies match org_name. 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) the company must belong to. Narrows which companies match org_name. 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.

  • org_location: Location group name or id where the company is based. Narrows which companies match org_name, so it may only be used together with org_name. Not case sensitive. Accepts multiple values. For stories that happened in a place use activity_location instead.

  • org_location_id: Location group identifiers (e.g., "Southern Asia", "BT", "US-CA") where the company is based. Case-sensitive. May only be used together with org_name.

  • org_name: Filter by organization name (partial match). (required)

  • 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 the company must work in. Narrows which companies match `org_name`. 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.
org_nameYesFilter by organization name (partial match).
page_sizeNoNumber of results to return per page.
industry_idNoIndustry ID (topic ID) the company must belong to. Narrows which companies match `org_name`. 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.
org_locationNoLocation group name or id where the company is *based*. Narrows which companies match `org_name`, so it may only be used together with `org_name`. Not case sensitive. Accepts multiple values. For stories that happened in a place use `activity_location` instead.
org_location_idNoLocation group identifiers (e.g., "Southern Asia", "BT", "US-CA") where the company is *based*. Case-sensitive. May only be used together with `org_name`.
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.
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.5/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavior. It does add meaningful context by enumerating 15 activity types (e.g., 'CorporateFinanceActivity,' 'IncidentActivity') that define what stories are included, and it clarifies deprecated aliases. However, it does not mention whether the operation requires authentication, has rate limits, or if it is read-only (though 'list' implies read). It also doesn't describe error scenarios or pagination behavior beyond the parameters. For a list endpoint with no annotations, this is adequate but not exhaustive.

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 well-structured with a summary, an extensive list of activity types, and parameter explanations. However, the long enumeration of 15 activity types is verbose and could be condensed without losing critical invocation details. The front-loaded summary is good, but the activity list adds bulk that may dilute focus. It's not overly long for the complexity, but it could be more concise.

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?

With 13 parameters, no output schema, and no annotations, the description covers a lot: the relationship between parameters, constraints (e.g., 'org_location' may only be used with 'org_name'), and references to other endpoints for valid values. It explains the 'output' parameter and pagination. While it doesn't describe the response structure (no output schema exists), it gives enough context for an agent to invoke the tool correctly. It is reasonably complete for a list endpoint.

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 description coverage is 100%, so the description adds value beyond the schema by providing examples (e.g., 'texas', 'india' for activity_location), clarifying case sensitivity, and explaining the difference between 'org_location' and 'activity_location.' It also cross-references other endpoints (location_groups, industry-clusters) and explains deprecated aliases. This goes well beyond the schema's bare descriptions.

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 clearly states the tool's purpose: 'Stories by Organization' and labels it a 'Simplified endpoint that runs the same logic as the main stories endpoint, with a restricted parameter set.' This goes beyond a tautology and clarifies the resource (stories) and filter (organization). However, it doesn't explicitly distinguish it from the sibling tool 'stories_industry_location_list' beyond mentioning 'main stories endpoint,' so it loses a point for not naming direct alternatives.

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 implies usage context by saying it's a 'simplified endpoint' with a restricted parameter set, but it does not explicitly state when to use this tool versus the main stories endpoint or the sibling 'stories_industry_location_list.' It also doesn't mention when not to use it. The context is clear (filter stories by organization) but lacks explicit alternative guidance.

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.3/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: location_groups_list provides reference data for location groups, register_and_get_key_create handles user authentication, and the two stories endpoints filter by different primary criteria (industry/location vs organization). The descriptions and required parameters make it easy to choose the right tool.

Naming Consistency2/5

Tool names follow no consistent pattern. Two end with '_list' but one is a multi-action verb phrase ('register_and_get_key_create'), and the stories endpoints mix descriptor order. This inconsistent naming could confuse agents trying to predict similar tool names.

Tool Count5/5

Four tools is a well-scoped size for a focused news API, covering authentication, location reference, and two primary story query paths. It avoids bloat while providing essential functionality.

Completeness3/5

The server covers story retrieval by industry/location and organization, but lacks a general story listing, an industry enumeration endpoint, or a way to fetch a single story by ID. These gaps may require agents to use workarounds or incomplete data.

Resources