Skip to main content
Glama

nosebleed.si guides

List all guides

list_guides
Read-onlyIdempotent

List every nosebleed.si guide, grouped by section, with its address and a one-line summary. Optionally only one section, e.g. "business", "ideas" or "basics".

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

Input Schema

NameRequiredDescriptionDefault
sectionNoOptional: only guides whose address or section contains this word.

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 readOnly, idempotent, non-destructive and closed-world, so safety needs no repeating. The description adds value beyond that by disclosing the response shape (grouped by section, address, one-line summary) and that the full set is returned ("every"), though it says nothing about result size or limits.

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: the first front-loads what is returned, the second covers the only optional variation. No filler, and every clause carries information.

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 enumeration with one optional parameter and no output schema, this covers what is returned and how to filter it. Absence of size/pagination guidance is the only real gap, and the site is unlikely to hold enough guides for that to be critical.

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 the section parameter. The description contributes concrete example values ("business", "ideas", "basics") but also slightly narrows the semantics by saying "only one section," whereas the schema states the word matches address or section.

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?

States a specific verb and resource ("List every nosebleed.si guide") and even names the return shape: grouped by section, with address and one-line summary. It does not explicitly contrast itself with search_guides or get_guide, so sibling differentiation is left implicit via the word "every".

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?

The second sentence explains the optional narrowing behavior ("only one section") with examples, which is genuine usage guidance for the single parameter. There is no statement about when to prefer search_guides or get_guide over this enumeration, so the agent must infer the alternative from names alone.

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.

Resources