Skip to main content
Glama

Syracuse Company News

by io.github.1145-am

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

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the tool's behavior by listing all activity types and explaining parameter constraints (e.g., org_location only with org_name, deprecated aliases). However, it does not mention pagination behavior, rate limits, or what happens with no results, which are common behavioral aspects.

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 quite long, with a large list of activity types that could be summarized or linked. While it is well-structured with clear sections, the activity type enumeration is verbose and could be condensed without losing essential information. The parameter list is also extensive, but each parameter has a clear description.

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?

Given the tool's complexity (13 parameters, no output schema), the description is fairly complete. It explains the activity types, parameter relationships, and deprecated aliases. However, it lacks information about the response structure beyond the output parameter, and the activity type list could be more concise. Overall, it provides enough context for an agent to use the tool effectively.

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 baseline is 3. The description adds significant value by explaining the distinction between activity_location and org_location, clarifying deprecated aliases, and providing examples for industry_context. It also explains the output parameter's default and options, which goes beyond 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 clearly states this is a simplified endpoint for stories by organization, with a restricted parameter set. It distinguishes itself from the main stories endpoint and lists the specific activity types it covers, making its 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 explains that this is a simplified version of the main stories endpoint and provides detailed parameter usage, including when to use org_location vs activity_location. However, it does not explicitly state when to use this tool versus the sibling tools like stories_industry_location_list, though the restricted parameter set implies its use case.

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