Skip to main content
Glama

Colorado Startups

Upcoming Colorado startup events

events
Read-onlyIdempotent

Events on the Colorado Startups calendar between two days, soonest first. Up to 25.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
toNoLast day, YYYY-MM-DD in Mountain Time
fromNoFirst day, YYYY-MM-DD in Mountain Time; today when left out
regionNophoton-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?

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description usefully adds result ordering and a hard cap of 25, but does not say whether more than 25 results exist or how to page past the cap, which matters for a capped list tool.

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

Conciseness4/5

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

Two compact sentences with the resource and scope front-loaded and no filler. The limit sentence could have been merged but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

All three parameters are optional and fully documented, and annotations cover the safety profile, so the basics are complete. However, with no output schema and no statement of what an event record contains, plus silence on behavior at the 25-result cap, an agent still lacks some information needed to interpret results.

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%: from, to and region all carry descriptions, formats and a default for from. The description only echoes the two-date framing and adds nothing about region or what happens when a range is omitted, so it is baseline-equivalent to the schema.

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?

Names a specific resource (Colorado Startups calendar events) with scope (between two days), ordering (soonest first) and a result cap (up to 25). It is clear what the tool returns, though it never explicitly contrasts itself with the sibling this_week, which overlaps in scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'between two days' — an agent can infer this is for arbitrary date-range queries. There is no explicit when-to-use, no exclusion, and no routing to this_week for the common 'what's on this week' case, leaving the agent to infer the distinction.

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.