Skip to main content
Glama

Colorado Startups

This week for Colorado founders

this_week
Read-onlyIdempotent

The events in the next 7 days, today included, in Mountain Time: up to 10, soonest first. Add a region to narrow it.

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": "this_week"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the description focuses on result-set behavior: timezone (Mountain Time), a hard cap of 10, and soonest-first ordering. That ordering and truncation context is genuinely useful and not derivable from annotations. It stops short of saying what happens when more than 10 events match.

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?

Two short sentences, front-loaded with the scope and its constraints (window, timezone, cap, order), then the optional filter. No filler and nothing redundant with the schema.

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

Completeness5/5

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

For a single-optional-parameter read tool with no output schema, the description supplies everything needed to call it correctly: the time window, timezone, result cap, sort order, and the effect of the one filter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the enum values are documented, so the baseline is 3. The description adds real meaning by framing 'region' as an optional narrowing filter, telling the agent that omitting it broadens rather than fails — information the schema alone does not convey.

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 a specific resource (events) and pins down the exact scope: next 7 days including today, Mountain Time, up to 10 results, soonest first. That window and cap distinguish it from the broader 'events' sibling, though it never names an alternative explicitly.

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?

'Add a region to narrow it' gives a clear cue for the optional parameter, and the time window implies when this tool applies. There is no explicit statement about when to prefer the general 'events' or 'region' siblings instead, so the routing guidance is only implied.

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.