Structured company & industry news for AI agents: typed, dated, source-linked events.
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.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | A page number within the paginated result set. | |
| page_size | No | Number of results to return per page. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It does not state whether this operation is read-only, whether pagination is supported, what the response format is, or any side effects. The description is entirely about the entity, not the tool's behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a multi-sentence paragraph explaining the data model. While not overly long, it spends time on context that is not directly tied to the tool's action. The structure is acceptable but not tightly focused on listing behavior.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of annotations and output schema, the description should explain what the tool returns, how pagination works, or any constraints. It only describes the concept behind the data, leaving a significant gap in understanding the tool's actual invocation and response.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% for the two parameters (page, page_size), so the schema fully documents them. The description adds no additional meaning to the parameters, so a baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explains what Location Groups are conceptually but does not explicitly state that the tool lists them. It lacks a clear verb like 'list' or 'get', and although the tool name implies the action, the description focuses on the data hierarchy rather than the operation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool vs. the sibling tools. It does not mention alternatives, conditions for use, or any exclusion criteria. The description only provides background on the data model, not usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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)
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | User email address |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears full responsibility. It discloses that an account is created, a verification email is sent, and an API token is returned. It also provides rate limit context (30 vs 300 queries/month), which is useful behavioral information. Minor gaps exist (e.g., duplicate email behavior), but overall it is quite transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences and front-loaded with the core action. The final sentence about emailing for more queries is slightly tangential but still relevant to quota context. It is concise without being overly terse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one param, no output schema), the description covers the main workflow: account creation, verification email, token return, and quota limits. It lacks failure-mode details but is otherwise complete enough for an agent to understand the tool's role.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% for the single email parameter, and the schema already describes it as 'User email address'. The description adds no extra semantic detail beyond the schema, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states the action: 'Creates a user account with the given email, sends a verification email, and returns an API token.' This is a specific verb+resource+outcome and clearly distinguishes from sibling list tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies this tool is for initial registration and obtaining a token, but it does not explicitly state when to use it versus alternatives or provide exclusions. It does mention quota implications for unverified vs verified users, but that's more about post-registration behavior.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | A page number within the paginated result set. | |
| output | No | Output format. Defaults to "simple" (SimpleStory schema). Use "full" for the detailed response. | |
| industry | No | Industry name to filter by. Accepts multiple values. | |
| location | No | Deprecated alias of `activity_location`, kept for backwards compatibility. It means the location the story happened in, not where the company is based. | |
| page_size | No | Number of results to return per page. | |
| industry_id | No | Industry 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_id | No | Deprecated alias of `activity_location_id`, kept for backwards compatibility. It means the location the story happened in, not where the company is based. | |
| industry_context | No | 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. | |
| activity_location | No | 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](#/location-groups/location-groups_list) endpoint. | |
| include_provenance | No | 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. | |
| activity_location_id | No | 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](#/location-groups/location-groups_list) endpoint. |
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.
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.
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.
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.
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.
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.
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.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | A page number within the paginated result set. | |
| output | No | Output format. Defaults to "simple" (SimpleStory schema). Use "full" for the detailed response. | |
| industry | No | Industry name the company must work in. Narrows which companies match `org_name`. Accepts multiple values. | |
| location | No | Deprecated alias of `activity_location`, kept for backwards compatibility. It means the location the story happened in, not where the company is based. | |
| org_name | Yes | Filter by organization name (partial match). | |
| page_size | No | Number of results to return per page. | |
| industry_id | No | 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](#/industry-clusters/industry-clusters_list) endpoint. | |
| location_id | No | 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 | No | 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 | No | 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`. | |
| industry_context | No | 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. | |
| activity_location | No | 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](#/location-groups/location-groups_list) endpoint. | |
| activity_location_id | No | 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](#/location-groups/location-groups_list) endpoint. |
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.
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.
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.
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.
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.
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.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
stories_industry_location_list6 fields changedInput schema / properties / activity_locationAdded value: +{
+ "description": "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](#/location-groups/location-groups_list) endpoint.",
+ "in": "query",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+}Input schema / properties / activity_location_idAdded value: +{
+ "description": "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](#/location-groups/location-groups_list) endpoint.",
+ "in": "query",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+}Input schema / properties / industry_context / descriptionPrevious value: -"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."New value: +"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."Input schema / properties / industry_idAdded value: +{
+ "description": "Industry 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.",
+ "in": "query",
+ "items": {
+ "type": "integer"
+ },
+ "type": "array"
+}Input schema / properties / location / descriptionPrevious value: -"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](#/location-groups/location-groups_list) endpoint."New value: +"Deprecated alias of `activity_location`, kept for backwards compatibility. It means the location the story happened in, not where the company is based."Input schema / properties / location_idAdded value: +{
+ "description": "Deprecated alias of `activity_location_id`, kept for backwards compatibility. It means the location the story happened in, not where the company is based.",
+ "in": "query",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+}stories_organization_list9 fields changedInput schema / properties / activity_locationAdded value: +{
+ "description": "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](#/location-groups/location-groups_list) endpoint.",
+ "in": "query",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+}Input schema / properties / activity_location_idAdded value: +{
+ "description": "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](#/location-groups/location-groups_list) endpoint.",
+ "in": "query",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+}Input schema / properties / industryAdded value: +{
+ "description": "Industry name the company must work in. Narrows which companies match `org_name`. Accepts multiple values.",
+ "in": "query",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+}Input schema / properties / industry_contextAdded value: +{
+ "description": "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.",
+ "in": "query",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+}Input schema / properties / industry_idAdded value: +{
+ "description": "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](#/industry-clusters/industry-clusters_list) endpoint.",
+ "in": "query",
+ "items": {
+ "type": "integer"
+ },
+ "type": "array"
+}Input schema / properties / locationAdded value: +{
+ "description": "Deprecated alias of `activity_location`, kept for backwards compatibility. It means the location the story happened in, not where the company is based.",
+ "in": "query",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+}Input schema / properties / location_idAdded value: +{
+ "description": "Deprecated alias of `activity_location_id`, kept for backwards compatibility. It means the location the story happened in, not where the company is based.",
+ "in": "query",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+}Input schema / properties / org_locationAdded value: +{
+ "description": "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.",
+ "in": "query",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+}Input schema / properties / org_location_idAdded value: +{
+ "description": "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`.",
+ "in": "query",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+}location_groups_listregister_and_get_key_createstories_industry_location_liststories_organization_listClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Private company data & real-time news signals for AI agents.
AI-enriched financial news for AI agents & trading bots: search, trending, insider, scored 1-10.
Evidence-backed capital-change intelligence and sourced financial data for AI agents
Company and market intelligence, news, enrichment, and agentic workflows for dealmakers.
Add one secure layer between your agents and this server.
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.
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.
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.
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.
