Skip to main content
Glama

Colorado Startups

A Colorado Startups region

region
Read-onlyIdempotent

One region: its summary, cities and counts, with up to 10 resources, 10 companies and 5 upcoming events.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "region"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesphoton-mountain, space-peak or fusion-canyon

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, closed-world and non-destructive behavior, so the safety profile is covered. The description does add one genuinely useful behavioral fact: the result caps (10 resources, 10 companies, 5 events), which tells an agent the response may be truncated. It stops short of saying whether those items are ordered, newest-first, or paginable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One compact sentence with the resource and payload contents front-loaded and nothing superfluous. It is dense but immediately readable.

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 no output schema, the description must describe return values, and it does so concretely, including per-type caps. Gaps remain around ordering, pagination behavior and what exactly the 'counts' represent, but for a single-id read tool it is largely sufficient.

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% and the single id parameter is a fully enumerated string, so the schema carries the parameter burden. The description adds no syntax or selection guidance for choosing between photon-mountain, space-peak and fusion-canyon, so the baseline of 3 applies.

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 names the resource (one region) and enumerates exactly what comes back: summary, cities, counts, plus capped resource, company and event lists. That is enough to distinguish it from the sibling tools (events, company, search, this_week), though the verb is implied rather than stated.

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 when-to-use guidance, no exclusion conditions, and no pointer to alternatives such as search or events for broader retrieval. The only usage signal is indirect, inferred from the returned payload.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.