Skip to main content
Glama

Colorado Startups

A founder's next steps

path
Read-onlyIdempotent

A short path for a founder at one stage: up to 5 Startup Resources, in the order of the stage's steps, each with one line on why it fits. Add what they need and their region to narrow it.

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": {
      "stage": "<stage>"
    },
    "name": "path"
  }
}

Input Schema

NameRequiredDescriptionDefault
needNoWhat the founder needs now, such as 'first customers' or 'hardware'
stageYesidea, launch, growth or support
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 establish read-only, idempotent, non-destructive behavior. The description adds useful output-level context: up to 5 resources, ordering by stage steps, and a one-line fit rationale per resource. It does not cover empty-result behavior or sourcing, but adds meaningful behavior beyond the annotations.

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 sentences, front-loaded with the core output shape and followed by optional filtering guidance. There is no redundant or filler wording.

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 appropriately explains the return shape: up to 5 resources, ordered, each with a one-line rationale. Input parameters are fully covered by schema descriptions, and annotations cover safety. Minor gaps remain around edge cases like no matching resources.

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 coverage is 100%, so the schema already documents all three parameters, including examples and enums. The description adds that need and region narrow results and that stage determines ordering, but does not provide substantial additional parameter semantics beyond that.

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 clearly states the tool returns a short path of up to 5 Startup Resources for a founder at one stage, ordered by the stage's steps, each with a rationale. It is specific about the resource and scope, though it does not explicitly distinguish this from sibling tools like guide or search.

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?

It indicates the core use case: a founder at a given stage, with optional narrowing by need and region. However, it gives no explicit when-not-to-use guidance or alternatives, leaving the agent to infer when this is preferable to siblings such as search or guide.

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.