Skip to main content
Glama

Colorado Startups

A founder guide

guide
Read-onlyIdempotent

One founder guide from coloradostartups.org/guides/: its title, summary and full answer, with a link. Find the slug with search, type guide.

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": {
      "slug": "<slug>"
    },
    "name": "guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe guide slug, such as 'startup-credits'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond them by disclosing the return payload (title, summary, full answer, link) and the slug-discovery prerequisite, which the annotations do not convey.

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 compact sentences with no filler: the first establishes what is returned, the second establishes the prerequisite. The essential scoping and return information is front-loaded.

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 one-parameter read-only lookup with no output schema, the description covers purpose, prerequisite, and return shape, which is everything an agent needs to call it correctly. No meaningful gap remains.

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 slug property already documents format with an example ('startup-credits'). The description adds meaning beyond the schema by explaining where the slug comes from (obtain it via `search` with type guide), which is the one thing the schema cannot say.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the exact resource (one founder guide from coloradostartups.org/guides/) and enumerates what comes back: title, summary, full answer, and a link. It is unmistakably the single-item fetcher rather than the list/searcher, and it points at the sibling that finds the slug.

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

Usage Guidelines4/5

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

Gives an explicit prerequisite workflow: 'Find the slug with search, type guide' tells the agent to call `search` filtered to type guide before invoking this tool. It stops short of stating when-not to use it (e.g., when no matching guide exists), but the sequencing guidance is concrete.

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.