Skip to main content
Glama

Syracuse Company News

by io.github.1145-am

location_groups_list

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.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

C2.5/5.0
Behavior2/5

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.

Conciseness3/5

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.

Completeness2/5

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.

Parameters3/5

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.

Purpose3/5

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.

Usage Guidelines2/5

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.

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