Skip to main content
Glama

Colorado Startups

Search Colorado Startups

search
Read-onlyIdempotent

Search Startup Resources, Leaderboard companies and guides by words. Filter by type and region. Up to 25 results, best first.

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": {
      "words": "<words>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoresource, company or guide; all three when left out
wordsYesWhat to look for, such as 'accelerator Boulder' or 'space'
regionNophoton-mountain, space-peak or fusion-canyon

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered. The description adds meaningful behavior beyond that: a hard cap of 25 results and relevance ordering ('best first'), which the agent needs to interpret result completeness.

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?

Three short sentences, front-loaded with the verb and scope, then filters, then result limits. No filler or redundancy.

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?

For a simple read-only search with full schema coverage and clear annotations, the description supplies the essentials plus result count and ranking. Only the absence of explicit alternative-tool routing keeps it from full marks.

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 both enum parameters carry their own descriptions, so the baseline is 3. The description restates that type and region act as filters but adds no syntax or format guidance beyond 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?

The description names a specific verb (Search) and a concrete resource scope (Startup Resources, Leaderboard companies, and guides), plus the search inputs (words, type, region). This clearly separates it from single-entity siblings like company, guide, or region, though no sibling is explicitly named.

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?

'Filter by type and region' implies how to narrow results, but there is no explicit when-to-use guidance or statement of when another tool (e.g. company, guide, region) would be the better choice. Usage must be inferred from the scope wording.

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.