Skip to main content
Glama

Syracuse Company News

Server Details

Structured company & industry news for AI agents: typed, dated, source-linked events.

Status
Healthy
Last Tested
Transport
Streamable HTTP
URL

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client
Glama
MCP server

Full call logging

Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.

Tool access control

Enable or disable individual tools per connector, so you decide what your agents can and cannot do.

Managed credentials

Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.

Usage analytics

See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.

100% free. Your data is private.

Tool Definition Quality

Score is being calculated. Check back soon.

Available Tools

4 tools
location_groups_listInspect

Location Groups are a way of grouping GeoNamesLocation entities into a simplified hierarchy.

They start from top-level regions using the United Nations M49 standard (Region/Sub-Region/Intermediate Region). The US is further broken down United States Census Bureau regions (e.g. East/West etc) and then into individual states. Certain other countries are also broken down into their states/provinces: AE, CA, CN, IN.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoA page number within the paginated result set.
page_sizeNoNumber of results to return per page.
register_and_get_key_createInspect

Creates a user account with the given email, sends a verification email, and returns an API token. Unverified users are limited to 30 queries/month; verified users can make 300/month for free. Drop us an email to tell us how you found the service and if you want more queries (see website footer)

ParametersJSON Schema
NameRequiredDescriptionDefault
emailYesUser email address
stories_industry_location_listInspect

Stories by Industry/Location Simplified endpoint that runs the same logic as the main stories endpoint, with a restricted parameter set (only industry and 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:

  • 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 (e.g. "Packaging" when searching for "Rigid Metal"). Applied to every value of industry in the same request.

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

  • 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.

ParametersJSON 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.
locationNoLocation group name or id (e.g. "texas", "india", "MidWest", "FR", "us-ca"). Not case sensitive. Accepts multiple values. They must each match an id or name from the [location groups](#/location-groups/location-groups_list) endpoint.
page_sizeNoNumber of results to return per page.
industry_contextNoOptional context aspects to anchor the industry search in. Pass each aspect as a separate value (e.g. "Packaging" when searching for "Rigid Metal"). Applied to every value of `industry` in the same request.
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.
stories_organization_listInspect

Stories by Organization Simplified endpoint that runs the same logic as the main stories endpoint, with a restricted parameter set (only org_name). 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:

  • 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.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoA page number within the paginated result set.
outputNoOutput format. Defaults to "simple" (SimpleStory schema). Use "full" for the detailed response.
org_nameYesFilter by organization name (partial match).
page_sizeNoNumber of results to return per page.

Discussions

No comments yet. Be the first to start the discussion!

Try in Browser

Your Connectors

Sign in to create a connector for this server.

Resources